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/setup)<a href="https://agentmods.dev/commands/keepwhatworks/trinity/setup"><img src="https://agentmods.dev/badge/commands/keepwhatworks/trinity/setup/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/setup"><img src="https://agentmods.dev/badge/commands/keepwhatworks/trinity/setup.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.00024 | $0.00212 |
| Opus 5.5 | $0.00010 | $0.00085 |
| Sonnet 5.5 | $0.00005 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
setup 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
If trinity-local is on PATH, run trinity-local install --check and relay its
report: for each CLI whether it is installed, signed in and registered, how many of
its transcripts Trinity reads, and which model its council member runs. It changes
nothing. Each gap comes with the command that fixes it; offer to run those.
If trinity-local is not on PATH, this plugin is running Trinity's MCP server on
its own, so the tools still work here. Say so, and that trinity-local install
(from the one-line installer on keepwhatworks.com) adds the CLI and registers
Trinity in Codex and agy too.
Do not run a council or verify here: this command only checks the setup. End with the single most important next step, not a wall of checks.
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 Changed · -22 lines · +3 tokens per session scan C → A 51ada956e2c9
- 1mo ago First seen · 40 lines · 21 tokens per session scan C c4a13e7fbd17
setup is a command published in the GitHub repository keepwhatworks/trinity (1 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session and 212 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 commands, from other repositories
prompt
A command that creates AI prompts and applies fixed rules for constraints, principles, and when the command may run.
prompt-sync
A command that synchronizes a prompt-generation system with a local folder, a personal vault, and a deployment repository. It keeps the same source structure across those locations.
prompt-update
A command for updating and combining prompt-engineering guidance, meaning methods for writing clearer instructions for AI.
auto-prompt
A command for automatically generating AI prompts in a format compatible with K-AI Station. The available description does not specify which prompt tasks or models it supports.
agy
Delegate any task to agy (Google Antigravity CLI) — auto-selects model by task type.
spec-research
A requirements-research command that turns a request into a set of constraints and checkable success criteria. It explores the relevant parts of a project in parallel and creates a structured proposal.