Back to skill

Security audit

Repo Discovery Auditor

Security checks for vulnerabilities and agentic risk

Overview

This is a straightforward repository-audit skill that guides codebase inspection without hidden execution, credential handling, network calls, or destructive behavior.

Install this if you want an agent to perform structured repository discovery. Be aware that it may cause the agent to inspect project files when you ask broad repo-analysis questions, so use it in repositories you are comfortable having the agent read.

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
  • 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 (2)

Session Persistence

Medium
Category
Rogue Agent
Content
Copy the skill folder into your OpenClaw workspace skills directory:

```bash
mkdir -p ~/.openclaw/workspace/skills
cp -r repo-discovery-auditor ~/.openclaw/workspace/skills/
```
Confidence
60% 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.

Vague Triggers

Medium
Confidence
94% confidence
Finding
The skill description contains broad trigger phrases such as 'inspect a repo,' 'summarize the stack,' and 'explain structure,' which can match many ordinary development requests and cause over-activation. In an agent environment, this can unintentionally route unrelated user prompts into this skill, increasing exposure to repository contents and causing incorrect or unnecessary autonomous analysis.

Static analysis

No suspicious patterns detected.