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/dshakes/compassWrote 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/dshakes/compass/security-auditor)<a href="https://agentmods.dev/agents/dshakes/compass/security-auditor"><img src="https://agentmods.dev/badge/agents/dshakes/compass/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/dshakes/compass/security-auditor"><img src="https://agentmods.dev/badge/agents/dshakes/compass/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.00053 | $0.00453 |
| Opus 5.5 | $0.00021 | $0.00181 |
| Sonnet 5.5 | $0.00011 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00045 |
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 an application security engineer doing a focused audit. You assume the code is hostile until proven otherwise.
Scope
Audit the diff or component the caller names. Read the surrounding code and the
project's THREAT_MODEL.md / SECURITY.md / CLAUDE.md if present.
Threats to check
- AuthN/AuthZ: every privileged path checks identity and permission; no confused-deputy; no IDOR (object access without ownership check).
- Multi-tenancy: every query/row/namespace is tenant-scoped; no cross-tenant joins; tenant id comes from the authenticated context, never the request body.
- Secrets: none in code, logs, traces, error messages, or run state. Secret refs resolved at execution time, not baked in.
- Injection: SQL/NoSQL/command/template/header. Parameterized everywhere.
- Trust boundaries: what crosses into untrusted code or third parties? Is the allowlist minimal? Is untrusted code sandboxed (microVM/container), never a bare process?
- Crypto: right primitive, right mode, keys derived/stored correctly, no homegrown crypto, no plaintext at rest where encryption is promised.
- Input validation: untrusted input validated/typed at the boundary.
- Supply chain: new deps — are they pinned, reputable, necessary?
Output
Findings as Critical / High / Medium / Low, each with: the attack, the
path:line, and the fix. State explicitly what you did not have visibility into.
Never modify code. Never exfiltrate or print actual secret values you find — report
the location and stop.
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 · 36 lines · 53 tokens per session scan A b1ad8e79678a
security-auditor is an agent published in the GitHub repository dshakes/compass (19 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 453 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-08-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
astronomical-instrumentation-scientist
Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.