Back to skill

Security audit

Coding Standards

Security checks for vulnerabilities and agentic risk

Overview

This skill is a plain coding standards reference with broad but disclosed activation terms and no runtime powers.

Install this as general coding guidance. Be aware it may activate on broad requests like code review or best practices, but the inspected package is documentation-only and does not run code or access sensitive data.

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
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • 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
Findings (2)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · references/api-design.md (reported line 11)May include surrounding context.

md
POST   /api/markets              # Create
PUT    /api/markets/:id          # Replace
PATCH  /api/markets/:id          # Update
DELETE /api/markets/:id          # Delete

# Query parameters for filtering
GET /api/markets?status=active&limit=10&offset=0

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger phrase list includes very broad terms such as "coding standards," "best practices," and "code review," which are likely to match many generic developer requests beyond the narrow scope of this skill. This can cause the skill to activate unexpectedly, leading to prompt hijacking of unrelated interactions or unnecessary injection of its guidance into contexts where it was not intended.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.