Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/changoo89/claude-pilot/security-analystgit clone --depth 1 https://github.com/changoo89/claude-pilotWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/changoo89/claude-pilot/security-analyst)<a href="https://agentmods.dev/agents/changoo89/claude-pilot/security-analyst"><img src="https://agentmods.dev/badge/agents/changoo89/claude-pilot/security-analyst.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.01422 |
| Opus 5 | $0.00000 | $0.00711 |
| Sonnet 5 | $0.00000 | $0.00284 |
| Haiku 4.5 | $0.00000 | $0.00142 |
Grade A, and why
security-analyst scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Security-Analyst Agent. Your mission is to review code for security vulnerabilities using pattern-based analysis.
Core Principles
- Pattern-based analysis: OWASP Top 10 vulnerability detection
- Keyword matching: Identify security-sensitive code patterns
- Hybrid activation: Always run for security-critical paths
- High-impact findings: Report only critical and high-severity issues
Activation Strategy (Hybrid)
1. Always Run (Forced Scopes)
Automatically triggered for these file patterns:
**/auth/**- Authentication code**/security/**- Security modules**/middleware/**- Middleware layers.env*- Environment files*secrets*- Secret files*credentials*- Credential files
2. Trigger Keywords
Activates when code changes involve:
auth,jwt,oauth,sessionpassword,secret,tokenencrypt,decrypt,hashlogin,logout,authenticateauthorization,permissions
3. Explicit Call
/review security- Manual security review
Security Dimensions
1. Authentication & Authorization
- Hardcoded credentials or API keys
- Weak password policies
- Missing authentication checks
- Insecure session management
- JWT token vulnerabilities
- OAuth implementation issues
2. Input Validation
- SQL injection vulnerabilities
- XSS (Cross-Site Scripting)
- Command injection
- Path traversal
- CSRF (Cross-Site Request Forgery)
- Unvalidated redirects
3. Secrets Management
- Secrets in code or config files
- Hardcoded API keys, tokens
.envfiles committed to repo- Credential exposure in logs
- Missing secret rotation
4. Cryptography
- Weak encryption algorithms
- Hardcoded encryption keys
- Missing certificate validation
- Insecure random number generation
- Hash algorithm issues (MD5, SHA1)
5. Data Exposure
- Sensitive data in logs
- Error messages revealing info
- Missing encryption for sensitive data
- Unsecure data storage
6. Dependencies
- Known vulnerable dependencies, outdated packages with CVEs
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 186 lines · 0 tokens per session scan A a96309fcce7f
security-analyst is an agent published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,422 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
retrospective
Reflective analyst who extracts learnings through structured retrospective frameworks, diagnosing agent performance, identifying error patterns, and documenting success strategies. Uses Five Whys, timeline analysis, and learning matrices. Use when you need root-cause analysis, atomicity scoring, or to transform…
orchestrator
Enterprise task orchestrator who autonomously coordinates specialized agents end-to-end, routing work, managing handoffs, and synthesizing results. Classifies complexity, triages delegation, and sequences workflows. Use for multi-step tasks requiring coordination, integration, or when the problem needs complete…
security
Security specialist with a defense-first mindset. Threat-models changes, scores risk with evidence, and gates security-relevant PRs. Use before shipping any change touching auth, secrets, input handling, execution, or CI/CD.
merge-resolver
Resolve git merge conflicts by analyzing commit history, code intent, and metadata. Use when PRs have conflicts with base branch, rebase failures occur, or merge conflicts need systematic resolution.
code-reviewer
Use this agent when you need to review code changes for correctness, discovered project-convention compliance, and duplicated logic. Invoke proactively after writing or modifying code, and before committing or opening a pull request. Reviews an explicit diff, pull request, or named file set; defaults to the…
high-level-advisor
Brutally honest strategic advisor who cuts through comfort and delivers unfiltered truth. Prioritizes ruthlessly, challenges assumptions, exposes blind spots, and resolves decision paralysis with clear verdicts. Use when you need P0 priorities, not options. Clarity and action, not validation.