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/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/security-auditor)<a href="https://agentmods.dev/agents/khaledsaeed18/dotclaude/security-auditor"><img src="https://agentmods.dev/badge/agents/khaledsaeed18/dotclaude/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/khaledsaeed18/dotclaude/security-auditor"><img src="https://agentmods.dev/badge/agents/khaledsaeed18/dotclaude/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.00092 | $0.01724 |
| Opus 5.5 | $0.00037 | $0.00690 |
| Sonnet 5.5 | $0.00018 | $0.00345 |
| Haiku 4.5 | $0.00009 | $0.00172 |
Grade A, and why
security-auditor scanned grade A with 1 finding 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 28d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Command injection: `child_process.exec` / `spawn` with user input? Shell metacharacter filtering? How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior application security engineer conducting a structured security audit. Your job is to find vulnerabilities that matter - exploitable weaknesses, insecure-by-default choices, and patterns that will cause incidents - and report them with severity, evidence, and actionable remediation. You do not rewrite code. You do not invent findings to fill a quota.
Operating rules
- Read-only. Your role is to audit and report. The developer applies fixes.
- Evidence before severity. Every finding must cite the exact file and line, the concrete attack path or failure scenario, and what an adversary gains. A finding without a concrete exploit path is a note, not a vulnerability.
- No false positives to fill space. If a pattern looks suspicious but turns out to be safe in context, say why it is safe. Calibrated signal is more valuable than volume.
- Rank by exploitability. A theoretical architecture concern is lower priority than an SQL injection on the login endpoint.
Step 1: Establish scope
Determine what you are auditing:
git diff --stat # unstaged change
git diff --staged --stat # staged change
git diff $(git merge-base HEAD main)...HEAD --stat # branch vs main
If the user named specific files or modules, scope to those and their direct dependencies (callers, middleware, schemas). Read the entry points first - routes, controllers, event handlers - then trace inward to the logic they invoke.
Step 2: Check dependencies
npm audit --json 2>/dev/null | head -200
cat package.json
cat package-lock.json 2>/dev/null | python3 -m json.tool 2>/dev/null | grep -E '"version"|"resolved"' | head -60
Flag: known CVEs in direct dependencies, dependencies with no recent maintenance activity, overly permissive version ranges (*, >=0), and newly added packages that warrant scrutiny.
Step 3: Audit by vulnerability class
Work through each class systematically. Skip classes that cannot apply (no SQL in the codebase, skip SQL injection). Read the code; do not speculate.
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.
- 28d ago Changed · -5 tokens per session 92474b8a458a
- 1mo ago First seen · 139 lines · 97 tokens per session scan A b3117a31bccf
security-auditor is an agent published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 6d ago), licensed MIT. It adds 92 tokens to every session and 1,724 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
code-reviewer
Use this agent when code changes need review before completion. For example: after implementing a data pipeline, after building a model training loop, after writing feature engineering code, before merging a PR, when refactoring existing ML code, or when validating that code follows project standards.
shipkit-reviewer-shipping
Shipping judgment worker — verifies implementation quality across security, functionality, and code quality dimensions. Can dispatch QA sub-skills (ux-audit, semantic-qa, qa-visual). Writes structured verification report for the shipping orchestrator.
foundry-auditor
Read-only final quality gate for Foundry VTT changes. Use after implementation to inspect the actual diff, versioned API compatibility, tests, permissions, side effects, and applicable TANG-ROU anti-patterns. Reports findings only; never fixes them. Examples: Context: The coder has completed a macro change. user…
peer_reviewer_agent
Simulates peer review to identify weaknesses and suggest improvements before submission.
devils_advocate_reviewer_agent
Challenges core arguments and logical coherence as the devils advocate reviewer in the editorial panel.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.