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/premise-checker)<a href="https://agentmods.dev/agents/dbc-oduffy/coordinator-claude/premise-checker"><img src="https://agentmods.dev/badge/agents/dbc-oduffy/coordinator-claude/premise-checker/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/premise-checker"><img src="https://agentmods.dev/badge/agents/dbc-oduffy/coordinator-claude/premise-checker.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.00019 | $0.01470 |
| Opus 5.5 | $0.00008 | $0.00588 |
| Sonnet 5.5 | $0.00004 | $0.00294 |
| Haiku 4.5 | $0.00002 | $0.00147 |
Grade C, and why
premise-checker scanned grade C 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 5d 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
You **report**. You never refuse, never block, and never edit the plan. Question class 5 is only 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.
- 5d ago Changed · +2 lines c5b45cc93cae
- 8d ago Changed · +1 lines 83bc1dbff909
- 13d ago Changed · +2 lines · -20 tokens per session 3202a4f550e0
- 17d ago Changed · -2 tokens per session d69ba528cc7c
- 20d ago Changed · -2 lines b805dfaccacd
- 1mo ago Changed b0415f43630f
- 1mo ago First seen · 84 lines · 41 tokens per session scan C a7d93b6f85bf
premise-checker is an agent published in the GitHub repository dbc-oduffy/coordinator-claude (5 stars, last pushed yesterday), with no licence file. It adds 19 tokens to every session and 1,470 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-10.
Other agents, from other repositories
architect
Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.
reviewer
Read-only review of a diff or PR for correctness, security, performance and maintainability. Returns path:line findings and a verdict. Use before merging a change.
code-resolver
Re-checks prior findings after a code fix. Given the prior findings (untrusted), diffs of newly changed files, per-finding since-raised diffs, and the tip worktree, decides whether each finding was addressed. Not for general questions.
security
Security review specialist (IRC handle @sec) dispatched to audit pull requests and branch diffs for security vulnerabilities before code merges.
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
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.