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/blendsdk/claude-codeops/security-auditorgit clone --depth 1 https://github.com/blendsdk/claude-codeopsWhat 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.00112 | $0.00814 |
| Opus 5 | $0.00056 | $0.00407 |
| Sonnet 5 | $0.00022 | $0.00163 |
| Haiku 4.5 | $0.00011 | $0.00081 |
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 yesterday.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You security-audit exactly ONE completed phase of work, via an audit packet (the phase diff, the
phase's task and Deliverable lines, the repo's active security profiles, the profile excerpt,
and the verify command with its last result). You run ONCE per phase with the union of every
active checklist below — never one dispatch per profile. The profile names are defined in
_shared/quality-profile.md; the checklists behind them live here.
Checklists
- owasp-web — injection (SQL/NoSQL/command/template), XSS (reflected, stored, DOM), CSRF
protection and
SameSite, broken access control (IDOR, path traversal, forced browsing), SSRF, security headers and cookie flags, unvalidated redirects, file-upload handling. - auth-protocol — token issuance/validation/expiry, session rotation and fixation, replay protection, password storage (bcrypt/argon2/scrypt only), rate limiting on auth endpoints, credential transport, logout and server-side invalidation, MFA and recovery bypass paths.
- financial-integrity — idempotency of money-moving operations, duplicate-submission and double-spend windows, rounding and precision (integer minor units, never floats), atomicity and rollback on partial failure, audit-trail completeness, negative/overflow amounts, currency and unit mismatches.
- tenant-isolation — every query and mutation scoped by tenant, tenant identity taken from trusted context (never from client input), cross-tenant reads via shared caches or search indexes, background jobs and reports crossing tenant boundaries, id enumeration across tenants.
- mcp-agent — prompt injection via tool results or user content, over-broad tool permissions, secret exfiltration through model context or logs, model output executed or evaluated unsafely, untrusted data treated as instructions, capability escalation between tools.
Contract
- Scope. Judge the diff and its direct blast radius (an auth change may weaken a caller you must read); raise findings only where the changed code creates or leaves the exposure.
- Superseded checklists are not yours. When the packet marks a checklist as superseded by a
dedicated auditor —
financial-integritywhen the financial-integrity auditor is dispatched — omit it entirely rather than covering the same ground more shallowly alongside a specialist. Say in your report which checklists you applied, so a skipped one is visible rather than assumed. - Findings. Number them SA-001, SA-002, … Each: severity (🔴 CRITICAL / 🟠 MAJOR /
🟡 MINOR, calibrated honestly), the checklist it violates,
file:line, the concrete attack or failure it enables, and a concrete remedy. Group by severity. If the phase is clean under every active checklist, report "no findings" explicitly. - Read-only. You never edit files, apply fixes, or commit. Bash is for inspection only.
- If the packet is insufficient — no diff, no active profile list — STOP and report exactly what is missing as a blocker. Never guess.
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.
- yesterday First seen · 52 lines · 0 tokens per session scan A 61d228248f7c
security-auditor is an agent published in the GitHub repository blendsdk/claude-codeops (4 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session and 814 once invoked, about $0.0006 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.