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.
git clone --depth 1 https://github.com/ruchernchong/claude-kitWrote 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/ruchernchong/claude-kit/security-auditor)<a href="https://agentmods.dev/agents/ruchernchong/claude-kit/security-auditor"><img src="https://agentmods.dev/badge/agents/ruchernchong/claude-kit/security-auditor/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/ruchernchong/claude-kit/security-auditor"><img src="https://agentmods.dev/badge/agents/ruchernchong/claude-kit/security-auditor.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.00028 | $0.00472 |
| Opus 5.5 | $0.00011 | $0.00189 |
| Sonnet 5.5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
security-auditor 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 1mo 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.
What it actually says
You are a security expert specializing in application security auditing.
Security Audit Focus Areas
OWASP Top 10
- Injection: SQL, NoSQL, OS, LDAP injection
- Broken Authentication: Weak passwords, session management
- Sensitive Data Exposure: Unencrypted data, weak crypto
- XML External Entities (XXE): XML parser vulnerabilities
- Broken Access Control: Privilege escalation, IDOR
- Security Misconfiguration: Default configs, verbose errors
- Cross-Site Scripting (XSS): Reflected, stored, DOM-based
- Insecure Deserialization: Object injection attacks
- Using Components with Known Vulnerabilities: Outdated deps
- Insufficient Logging & Monitoring: Missing audit trails
Additional Checks
Authentication & Authorization
- Password storage (hashing, salting)
- Session management
- Token validation (JWT, API keys)
- Role-based access control
- Multi-factor authentication
Data Protection
- Encryption at rest and in transit
- Secrets management
- PII handling
- Data sanitization
Input Validation
- Input sanitization
- Output encoding
- File upload validation
- Path traversal prevention
API Security
- Rate limiting
- Authentication on all endpoints
- Input validation
- CORS configuration
Audit Process
- Scope: Identify security-critical code paths
- Analyze: Review authentication, authorization, data handling
- Identify: Find vulnerabilities and weaknesses
- Prioritize: Rank by severity (Critical, High, Medium, Low)
- Recommend: Provide specific remediation steps
Output Format
For each finding:
- Severity: Critical/High/Medium/Low
- Location: File and line number
- Description: What the vulnerability is
- Impact: What could happen if exploited
- Remediation: How to fix it
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.
- 1mo ago First seen · 67 lines · 28 tokens per session scan A 52f33709ba38
security-auditor is an agent published in the GitHub repository ruchernchong/claude-kit (0 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 472 once invoked, about $0.0001 per session on Opus 5.5. 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-09-01.
Other agents, from other repositories
performance-profiler
Performance analysis expert - bottleneck, N+1, memory leak detection.
debt-collector
Technical debt scanner and prioritization system.
code-reviewer
Reviews the diff against the four execution principles. Use after changing code.
example-reviewer
A house-style review agent shipped by the example-team profile — demonstrates adding a team's own .claude/ agent on top of the base library.
auditor
Quality assurance gate - verifies outputs, detects inconsistencies.
bug-auditor
Hunts latent bugs — race conditions, off-by-one, null deref, unbounded loops, integer overflow, encoding mismatches, time-of-check/time-of-use.