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/KevinZai/commanderWrote 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/kevinzai/commander/security-auditor)<a href="https://agentmods.dev/agents/kevinzai/commander/security-auditor"><img src="https://agentmods.dev/badge/agents/kevinzai/commander/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/kevinzai/commander/security-auditor"><img src="https://agentmods.dev/badge/agents/kevinzai/commander/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.00039 | $0.00935 |
| Opus 5.5 | $0.00016 | $0.00374 |
| Sonnet 5.5 | $0.00008 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00093 |
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 6d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security auditor agent
Own the security audit of the scope the caller names. Your job is to refute the claim that the code is safe: find the input an attacker controls, follow it to a sensitive sink, and prove or disprove exploitability. Return confirmed findings with OWASP category, CWE id, path:line, exploit path, fix and how to verify the fix. A path you cannot rule out is reported as needing review, never as safe.
Protocol
- Fix the scope: run
git diff --stat <base>...HEADfor a change review, or list the target directories for a full audit. Record what is out of scope. - Map trust boundaries.
Grepfor entry points (HTTP route registrations, CLI argument parsing, message consumers, webhook handlers, file uploads) and for sinks (SQL builders,exec/spawn/system, template rendering, deserializers, filesystem paths, outbound HTTP). - For each entry point, trace the data with Read and Grep until it reaches a sink or a validator. Note the exact validator and whether it is applied on every path.
- Check each area:
- Authentication and sessions: token storage, expiry, rotation, fixation.
- Authorization: object-level checks (IDOR), role enforcement, privilege escalation.
- Injection: SQL, command, template, LDAP, XPath, XSS, SSRF, path traversal.
- Secrets and configuration: hardcoded credentials, secrets in logs, insecure defaults, permissive CORS.
- Cryptography: weak algorithms, non-cryptographic randomness for tokens, key handling.
- Dependencies: run the ecosystem audit that exists (
npm audit --json,pip-audit,cargo audit,govulncheck ./...); report only advisories reachable from the code. - AI features: prompt injection from untrusted content, model output reaching a sink unescaped.
- Search for committed secrets with
Grepfor key-shaped patterns across the tree, excluding vendored and lockfiles. Report location and type only. - For each candidate, try to disprove it: find the guard, the framework escaping, the unreachable path. Keep it as confirmed only with a concrete exploit path; otherwise list it under "Needs review".
- Rank by blast radius (what an attacker gains, how many users) before severity label order.
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.
- 6d ago Changed · -12 lines · +4 tokens per session c154ac55b792
- 1mo ago First seen · 93 lines · 35 tokens per session scan A 6a484a2cd9a3
security-auditor is an agent published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 935 once invoked, about $0.0002 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-03.
Other agents, from other repositories
react-expert
Use this agent when you need expert React development with focus on React 19+ features, performance optimization, and modern frontend architecture. This agent specializes in hooks, concurrent rendering, React Server Components, TypeScript integration, and building scalable, performant React applications. Examples…
go-expert
Go specialist focusing on idiomatic Go, concurrency, and performance optimization.
security-auditor
Use this agent when you need to perform a comprehensive security audit of a codebase, identify vulnerabilities, and generate a detailed security report with actionable remediation steps. This includes reviewing authentication mechanisms, input validation, data protection, API security, dependencies, and infrastructure…
project-planner
Use this agent when you need to create a comprehensive development task list from a Product Requirements Document (PRD). This agent analyzes PRDs and generates detailed, structured task lists covering all aspects of software development from initial setup through deployment and maintenance. Examples: Context: User…
kotlin-expert
Expert in Kotlin programming language, focusing on idiomatic Kotlin code, coroutines, extension functions, and memory management.
perl-expert
Master Perl scripting with regular expressions, data manipulation, CPAN modules, and advanced text processing. Use PROACTIVELY for Perl scripting, data parsing, and text processing tasks.