Back to skill

Security audit

Update Docs on Code Change

Security checks for vulnerabilities and agentic risk

Overview

This skill is a documentation helper whose broad activation wording may cause extra doc edits, but its behavior is disclosed and limited to project documentation updates.

Install this if you want the agent to proactively keep docs aligned with user-facing code changes. Review proposed documentation edits for relevance, especially on internal refactors or test-only changes where documentation may not actually need to change.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill metadata uses broad trigger language such as 'automatically update' and lists many common development events, which can cause over-invocation in ordinary coding workflows. In an agentic environment, ambiguous activation boundaries can lead to unintended documentation edits, unnecessary file modifications, and noisy commits that affect repository integrity and developer trust.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The body reinforces autonomous detection and execution without defining when the skill should not activate, making it prone to matching many routine code changes. This increases the chance of unauthorized or low-signal documentation churn, and in multi-skill systems could cascade into broader automated actions based on incorrect assumptions about required doc updates.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.