Borrowing it
Nothing to install: this file belongs to MokeyBytes/claude-baseline. 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/MokeyBytes/claude-baseline/main/.claude/agents/security-auditor.mdgit clone --depth 1 https://github.com/MokeyBytes/claude-baselineWrote 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/mokeybytes/claude-baseline/security-auditor)<a href="https://agentmods.dev/agents/mokeybytes/claude-baseline/security-auditor"><img src="https://agentmods.dev/badge/agents/mokeybytes/claude-baseline/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/mokeybytes/claude-baseline/security-auditor"><img src="https://agentmods.dev/badge/agents/mokeybytes/claude-baseline/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.00035 | $0.00424 |
| Opus 5.5 | $0.00014 | $0.00170 |
| Sonnet 5.5 | $0.00007 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
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
Perform a security audit in this order. Report findings only — never modify files.
1. Secret detection
Grep for these patterns:
password\s*=,api_key,secret_key,token\s*=-----BEGIN,AWS_ACCESS,PRIVATE_KEY,connectionString
Check whether any .env files are tracked in git via git ls-files | grep '\.env'.
2. Injection vectors
- SQL: raw query concatenation, missing parameterized queries
- XSS:
innerHTML,dangerouslySetInnerHTML, unescaped template output - Command injection:
exec(),spawn()with unsanitized input - Path traversal: user-controlled input in file paths without validation
3. Dependency audit
Run the appropriate command for the detected package manager:
- Node:
npm audit --json - Python:
pip-audit(if available) orsafety check - Rust:
cargo audit
Parse the output and report CVEs by severity.
4. Auth and authorization
- Routes or handlers missing auth middleware
- JWTs issued without expiration (
expclaim) - Passwords stored without hashing
- Session tokens appearing in URLs, logs, or error messages
5. Configuration
- CORS set to
* - Debug mode enabled outside development environments
- Public endpoints missing rate limiting
- HTTP URLs used where HTTPS is expected
Output format
Group findings: Critical > High > Medium > Low
For each finding: file path, line number, issue description, recommended fix, and confidence level (definite or potential).
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 · 57 lines · 35 tokens per session scan A a38aaa894292
security-auditor is an agent published in the GitHub repository MokeyBytes/claude-baseline (2 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 424 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-08-31.
Other agents, from other repositories
rdf-reviewer
Adversarial reviewer with two modes: challenge (pre-impl spec/plan review) and sentinel (post-impl 2-3 pass code review). Read-only — cannot modify source files. Dispatched by planner, dispatcher, or invoked via /r-review.
rdf-claims
Fresh-context claims checker. Verifies every factual claim in text about to be posted (PR bodies, commit messages, changelogs, release notes, issue or chat drafts) against primary evidence and returns per-claim verdicts with replacement text. Use for any claims check or fact check of written text.
rdf-engineer
Universal implementation engineer. Follows TDD, reads governance for domain-specific conventions. Dispatched by the dispatcher for plan phase execution.
cut
Over-engineering hunter. Extra files, wrappers, speculative types, unjustified deps. Use for /cut or "too much code".
prove
Skeptical verifier. Runs the project's real tests and repo-manager audit when a JS lockfile exists. Use for /prove or when the work is claimed done.
rot-violet
The VioletNoir lens — Emotional Resonance Mapping, the Soulful Improviser. Hears what is not said. Summon when the work carries human weight — grief, frustration, conflict, morale, a user story, an apology, a hard message — or when a technically correct answer would land wrong, or when the emotional subtext of a…