Borrowing it
Nothing to install: this file belongs to changoo89/claude-pilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/changoo89/claude-pilot/main/.claude/agents/security-analyst.mdgit 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01422 |
| Opus 5.5 | $0.00000 | $0.00569 |
| Sonnet 5.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 2mo 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.
- 2mo 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 8mo 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
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
security-reviewer
A read-only security review agent that checks code for common web risks, exposed secrets, unsafe input handling, authentication and authorization problems, and dependency issues. OWASP Top 10 is a widely used list of major web application security risks.
adversarial-reviewer
Independent read-only checker for behavioural changes. Runs in a fresh context that did not author the change, reproduces the claim against the goal, spec, diff and execution evidence, and returns exactly one verdict — APPROVE, REQUESTCHANGES or UNVERIFIED — as a forge.review/v1 envelope. MUST BE USED before claiming…
database-reviewer
Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.