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/dbc-oduffy/coordinator-claudeWrote 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/dbc-oduffy/coordinator-claude/test-evidence-parser)<a href="https://agentmods.dev/agents/dbc-oduffy/coordinator-claude/test-evidence-parser"><img src="https://agentmods.dev/badge/agents/dbc-oduffy/coordinator-claude/test-evidence-parser/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/dbc-oduffy/coordinator-claude/test-evidence-parser"><img src="https://agentmods.dev/badge/agents/dbc-oduffy/coordinator-claude/test-evidence-parser.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.00022 | $0.01656 |
| Opus 5.5 | $0.00009 | $0.00662 |
| Sonnet 5.5 | $0.00004 | $0.00331 |
| Haiku 4.5 | $0.00002 | $0.00166 |
Grade A, and why
test-evidence-parser 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 21d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 21d ago Changed · -2 lines · -11 tokens per session 0107f5793fda
- 1mo ago Changed dd79fd8ed486
- 1mo ago First seen · 122 lines · 33 tokens per session scan A 2b5b4094b77e
test-evidence-parser is an agent published in the GitHub repository dbc-oduffy/coordinator-claude (6 stars, last pushed today), with no licence file. It adds 22 tokens to every session and 1,656 once invoked, about $0.0001 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-31.
Other agents, from other repositories
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
session-reviewer
Use this agent between waves or at session end to verify work quality against the session plan, or ad hoc to review a named diff, branch or MR without any plan (verdict ship / ship nach Fix / FIXREQUIRED). Checks implementation correctness, test coverage, TypeScript health, security basics, and issue tracking accuracy.
Inspektor jakości z checklista
QA Quality to audytor jakości kodu i zgodności ze specyfikacja. Jego misja: zweryfikować czy artefakt robi to co powinien, czy testy pokrywają scenariusze, czy kod jest czytelny i wydajny. Działa równolegle do QA Security ale z całkowicie inna perspektywa - poprawność zamiast bezpieczeństwa.
qa-tester
The QA Tester of the aSPARK team. Use in the Review phase (/demo-day) to test the running application hands-on in a real browser: verify every acceptance criterion from the spec, explore beyond the happy path, check console and network, and file reproducible bugs. Requires a browser integration (Claude in Chrome…
security
Security review specialist (IRC handle @sec) dispatched to audit pull requests and branch diffs for security vulnerabilities before code merges.
review
Correctness/quality review specialist (IRC handle @rev) dispatched to audit pull requests and branch diffs for bugs, regressions, and maintainability issues before code merges, alongside @sec's security pass.