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/keepwhatworks/trinityWrote 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/commands/keepwhatworks/trinity/verify)<a href="https://agentmods.dev/commands/keepwhatworks/trinity/verify"><img src="https://agentmods.dev/badge/commands/keepwhatworks/trinity/verify/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/commands/keepwhatworks/trinity/verify"><img src="https://agentmods.dev/badge/commands/keepwhatworks/trinity/verify.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.00020 | $0.00231 |
| Opus 5.5 | $0.00008 | $0.00092 |
| Sonnet 5.5 | $0.00004 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
verify 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 17d 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
Call the mcp__trinity-local__verify tool on the change you just made.
diff: the unified diff of the change (git diff, orgit diff HEAD~1if it is committed).criteria: for each test that exercises the changed files, an item{id, kind: "test", statement, command}with the command this project already uses (pytest, npm test, cargo test...), never one you invented; plus the claim under test as{id, kind: "judgment", statement}.exclude_lab: your own lab, so another lab reads your work.
Relay the result exactly. STOP: a relevant test is red; say which. READ: a person still reads; name what is unverified. The other labs' read is a second opinion, not approval. What the change is for: $ARGUMENTS
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.
- 17d ago First seen · 18 lines · 20 tokens per session scan A bd23871861e3
verify is a command published in the GitHub repository keepwhatworks/trinity (1 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 231 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-10-04.
Other commands, from other repositories
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
test-value-review
Use when a diff adds or changes test files, when a PR claims coverage for config, CI workflows, templates, or HTML output, or when tests look written only to satisfy a "must have tests" rule; not for Playwright selector or performance hygiene (use /playwright-review).
COMMAND_COMPLIANCE_REPORT
Reviewed all command files in .claude/commands/analysis/ directory to ensure proper usage of.
tldr-review
One-line TLDR PR review comments (verdict first, no filler).
claude-loop
Use a fresh headless Claude session (Fable by default) as an independent reviewer of the whole repo, area by area (or of one branch's diff with --base), fix every real finding with regression tests, and loop until each area comes back clean twice in a row. The /codex-loop pattern on Anthropic usage. Runs autonomously.
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.