Back to skill

Security audit

Agent Stack Audit

Security checks for vulnerabilities and agentic risk

Overview

This is a plausible maintenance-audit skill, but it asks an agent to inspect sensitive operational data too broadly and permits limited code changes without a clear approval gate.

Install only if you are comfortable giving the agent a narrowly scoped maintenance-audit role. Before running it, specify exact directories, scheduled jobs, accounts, and memory files in scope; prohibit reading or storing secret values; require redaction in reports; and require explicit approval for every code or cleanup change.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (4)

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
SKILL.md:32
Finding

Unbounded System and Process Reconnaissance

Content
View full analysis
Remediation
View remediation

T05 · Unauthorized Access and Privilege Escalation

Error
Location
SKILL.md:52
Finding

Unsafe Discovery and Reporting of API Credential Inventory

Content
View full analysis
Remediation
View remediation

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
SKILL.md:61
Finding

Unbounded Inspection of Installed Skills and Persistent Agent Context

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:132
Finding

Unauthorized Source Modification Through Cleanup Exception

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Rogue AgentSelf-Modification, Session Persistence
  • 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 (3)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The manual trigger condition is broad enough that ordinary user complaints like unexpected bills or degraded reliability could invoke a high-scope audit over crons, scripts, API keys, memories, and subscriptions without clear confirmation boundaries. In an agent environment, ambiguous invocation increases the chance of unintended reconnaissance across sensitive operational data and can lead to risky follow-on recommendations or edits.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The listed trigger phrases are common conversational requests that could easily appear in normal dialogue, causing accidental activation of a privileged maintenance workflow. Because this skill inspects scheduled tasks, scripts, keys, memory files, and tools, accidental invocation expands access to sensitive metadata and increases the chance of unintended state changes later in the workflow.

Content

No source excerpt is available for this finding.

Session Persistence

Medium
Category
Rogue Agent
Confidence
75% confidence
Finding

Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.

Content

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

md
### 1. Crons — Are they alive and earning their keep?

For each launchd agent / cron job / scheduled task:
- Is the process actually running? (check PID, plist/cron status)
- When did it last fire successfully?
- What does it produce? Is that output being consumed by anything?
- Is there a newer/better approach that renders this obsolete?