Back to skill

Security audit

Systematic Debugging

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent debugging-process skill, but users should be careful with its example diagnostics because they can print credential-adjacent signing and keychain metadata.

Install this if you want a strict root-cause debugging workflow. Avoid running or logging the keychain/signing diagnostic examples in CI, production, or shared support channels without redacting environment and signing identity details.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • 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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Credential Access

High
Category
Privilege Escalation
Confidence
87% confidence
Finding

The skill recommends diagnostic commands that enumerate keychain state and signing identities during troubleshooting. Even without extracting secrets, this can disclose sensitive environment details, certificate presence, account naming, or security posture into logs visible to users, CI systems, or third-party log collectors.

Content

Scanner excerpt · SKILL.md (reported line 104)May include surrounding context.

md
env | grep IDENTITY || echo "IDENTITY not in environment"

   # Layer 3: Signing script
   echo "=== Keychain state: ==="
   security list-keychains
   security find-identity -v

Credential Access

High
Category
Privilege Escalation
Confidence
88% confidence
Finding

The example explicitly includes security list-keychains and security find-identity -v, which can expose sensitive operational metadata during debugging. In a debugging skill, users may copy these commands into production or CI environments, increasing the chance that credential-adjacent information is unnecessarily logged or retained.

Content

Scanner excerpt · SKILL.md (reported line 105)May include surrounding context.

md
# Layer 3: Signing script
   echo "=== Keychain state: ==="
   security list-keychains
   security find-identity -v

   # Layer 4: Actual signing

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The description says to use the skill when encountering 'any bug, test failure, or unexpected behavior,' which is extremely broad and lacks limiting context or exclusion conditions. This can overlap with many ordinary development interactions and may cause the skill to be invoked more often than intended.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The 'When to Use' section instructs use for 'ANY technical issue' and then lists a wide range of common engineering situations. Because it does not define exclusions or a narrower trigger scope, the activation condition is ambiguous and risks unintended invocation across routine tasks.

Content

No source excerpt is available for this finding.