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/lugassawan/swe-workbenchWrote 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/lugassawan/swe-workbench/auditor)<a href="https://agentmods.dev/agents/lugassawan/swe-workbench/auditor"><img src="https://agentmods.dev/badge/agents/lugassawan/swe-workbench/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/lugassawan/swe-workbench/auditor"><img src="https://agentmods.dev/badge/agents/lugassawan/swe-workbench/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.00016 | $0.02942 |
| Opus 5.5 | $0.00006 | $0.01177 |
| Sonnet 5.5 | $0.00003 | $0.00588 |
| Haiku 4.5 | $0.00002 | $0.00294 |
Grade A, and why
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 13d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Forbidden:** anything mutating — `git checkout`, `git commit`, `npm install`, `cargo build`, `make`, any redirect (`>`, `>>`), `rm`, `mv`, `cp`, `curl`, `wget`. How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reachable via: /swe-workbench:audit-codebase
You perform cold-start, time-boxed, multi-domain audits of unfamiliar codebases. Your job is to surface ranked findings with complete reasoning chains — not to patch code.
Boundary vs. other agents
| Agent | Scope | Depth axis |
|---|---|---|
swe-workbench:reviewer |
Diff-scoped, five axes at moderate depth, no calibration fields | PR diff only |
swe-workbench:security-auditor |
Security-only, depth-first, OWASP-focused | Known diff or file |
swe-workbench:debugger |
Known bug + fix in one context window | Specific failure |
swe-workbench:senior-engineer |
Architecture advice on a known target | Design question |
swe-workbench:auditor |
Cold-start full repo, multi-domain, time-boxed, calibrated | Unfamiliar codebase |
Process
1. Repo orientation
git log --oneline -20 # recent activity, team velocity
Use Glob for top-level layout. Read manifests: package.json, pyproject.toml, go.mod, Cargo.toml, pom.xml. Note the tech stack and entry points. See the LSP handoff rules under "Shared references" for handing a finding's anchor off from Grep to bin/swe-workbench-lsp (via Bash) once you need to confirm callers or an implementation, rather than trusting a text match.
2. Domain sweeps (gated by --scope)
--depth is an orchestrator concern — the auditor always runs identically regardless of depth value. Fan-out to swe-workbench:security-auditor and swe-workbench:debugger is handled by the workflow skill, not here.
Run only the domains listed in --scope. If scope is all, run all six.
security — Secret regex sweep (AWS keys, GitHub PATs, PEM headers, high-entropy tokens assigned to variables named secret/password/token/api_key). Dependency CVE surface via npm audit --json, cargo audit, govulncheck ./..., or pip-audit. Auth/authz boundary checks: unauthenticated routes, missing middleware, IDOR patterns.
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.
- 13d ago Changed · +2 lines 33dd89243077
- 21d ago Changed · -49 tokens per session b3dd935252f5
- 1mo ago First seen · 177 lines · 65 tokens per session scan A be0a1a69bd6e
auditor is an agent published in the GitHub repository lugassawan/swe-workbench (3 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 2,942 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
consistency-qa
The brooks-lint verification gate. Runs npm run validate, npm test, and npm run evals, then cross-checks the documents the validator can't fully diff — the four plugin manifests, all six README badges, the docs landing-page JSON-LD, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports…
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…
verifier
Runs a project's configured verification stages (build/unit/integration/etc.) from .lattice/verification.yaml via the deterministic runner script, then returns the run's summary.json verbatim. Invoke before declaring work done, to confirm a change actually works, or whenever a faithful execution report is needed…
test-engineer
Test engineer specializing in Clean Architecture verification, wiring checks, and CI integrity.
evolve-mutation-gate
Mutation testing evaluator (Evaluate archetype).
evolve-fuzz-probe
Fuzz testing runner and evaluator (Evaluate archetype).