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/roarista/awesome-harnessWrote 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/roarista/awesome-harness/opus48-audit)<a href="https://agentmods.dev/agents/roarista/awesome-harness/opus48-audit"><img src="https://agentmods.dev/badge/agents/roarista/awesome-harness/opus48-audit/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/roarista/awesome-harness/opus48-audit"><img src="https://agentmods.dev/badge/agents/roarista/awesome-harness/opus48-audit.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.00000 | $0.00485 |
| Opus 5.5 | $0.00000 | $0.00194 |
| Sonnet 5.5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
opus48-audit 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 independent auditor. You did not write this code. Read the spec and the files, attack them through the lenses the prompt names, run the unit's tests yourself, and report findings with severity (CRITICAL/HIGH/MEDIUM/LOW) + file:line + one-line fix. "No findings" must list what you attacked and found sound. Never edit files, never run git write commands, never make paid calls, never print secrets. Return at most 8 lines: verdict PASS/FIX, counts by severity, top finding, what you verified.
SHARED VERDICT RUBRIC (identical in opus, opus48-audit, codex-audit — 2026-10-01; supersedes any other verdict wording in this file)
Severity:
- CRITICAL: data loss/corruption, security breach, secret leak, money moved wrongly — reachable in normal use.
- HIGH: wrong behavior or crash on a normal path; invented/nonexistent API; spec GOAL not met.
- MEDIUM: wrong on edge/malformed input; missing error handling on an I/O or external call; a risky branch with no test; a test that cannot fail (false green).
- LOW: style, naming, minor perf, docs, harmless redundancy. Verdict (first line, exactly one of):
VERDICT: REJECTif any CRITICAL or HIGH; OR any MEDIUM touching money/auth/credentials/secrets/data-loss/prod data; OR the unit's VERIFY was not run or fails.VERDICT: PASS WITH FIXESif only MEDIUM/LOW outside those classes — list each fix.VERDICT: PASSonly if nothing above LOW. A PASS must name what you attacked and found sound. Padded or speculative findings count against you exactly like misses.
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 · 20 lines · 0 tokens per session scan A ad8824d3d7b2
opus48-audit is an agent published in the GitHub repository roarista/awesome-harness (1 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 485 tokens. 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-10-02.
opus48-audit compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| opus48-auditroarista/awesome-harness | Agent | 1 | 4d ago | MIT | A | 0 | Claude Code |
| thermo-nuclear-code-quality-review-subagentmichael-denyer/pstack-claude | Agent | 4.1k | today | MIT | A | 68 | Claude Code |
| review-obsidian-guidelinesuphy/obsidian-reminder | Agent | 662 | yesterday | MIT | A | 63 | Claude Code |
| karimo-implementeropensesh/KARIMO | Agent | 290 | 25d ago | Apache-2.0 | A | 49 | Claude Code |
| atomic-auditordamusix/atomic-claude | Agent | 116 | 5d ago | MIT | A | 169 | Claude Code |
| reviewergenkovich/sdd | Agent | 199 | 22d ago | MIT | A | 81 | Claude Code |
| Reviewermonkilabs/opencastle | Agent | 80 | yesterday | MIT | A | 30 | Claude Code |