setup

A command that checks and repairs a Trinity-Local installation, including its command-line engine, health status, and MCP registration. MCP is a standard way for an agent to connect to external tools.

In plain words
What is it for?
Use it after installing Trinity-Local or when it is not working, to check PATH settings, health, the local embedder download, and registration with supported coding-agent applications.
Why use it?
It replaces a scattered setup check with a guided checklist and fixes the parts it can, while identifying the few steps that still need the user.

Command

Install

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.

agentmods
npx agentmods add commands/keepwhatworks/trinity/setup
Clone the repo
git clone --depth 1 https://github.com/keepwhatworks/trinity
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 541 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.00541
Opus 5 $0.00010 $0.00270
Sonnet 5 $0.00004 $0.00108
Haiku 4.5 $0.00002 $0.00054

Measured yesterday against content hash c4a13e7fbd17, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

setup scanned grade C with 2 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 yesterday.

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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

`curl -fsSL https://raw.githubusercontent.com/keepwhatworks/trinity/main/scripts/install.sh | bash`

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

`curl -fsSL https://raw.githubusercontent.com/keepwhatworks/trinity/main/scripts/install.sh | bash`
plugins/trinity-local/commands/setup.md · 40 lines

What it actually says

Verify the Trinity-Local install end to end and fix what you can, then tell the user the one or two things only they can do. Work through these in order and report a short checklist (✅ / ⚠️ / ❌ per item):

  1. Engine on PATH. Run trinity-local --version (or command -v trinity-local).

    • If it's missing, the runtime isn't installed (there is no PyPI/npm package). Tell the user to run the one-line installer and stop: curl -fsSL https://raw.githubusercontent.com/keepwhatworks/trinity/main/scripts/install.sh | bash
    • If it runs but only via an absolute path, ~/.local/bin likely isn't on PATH — tell the user to add export PATH="$HOME/.local/bin:$PATH" to their shell rc (this is the one step the installer can't do for them).
  2. Health. Run trinity-local status. Surface any check that reports a fix field verbatim. If it reports the embedder isn't downloaded, note that real embeddings (and the personalized taste read) need a one-time trinity-local download-embedder (~600 MB, local).

  3. MCP registered. Run trinity-local install-mcp to (re)write the MCP server config into every harness it detects (Claude Code, Codex CLI, Antigravity, Cursor). It's idempotent — safe to re-run.

  4. Restart reminder. Adding or re-registering MCP tools needs the harness to reload. Tell the user to restart this harness (or run /reload-plugins in Claude Code) so the mcp__trinity-local__* tools appear — this is the second step the CLI can't do for them.

  5. Smoke. If the MCP tools are already visible, call mcp__trinity-local__get_persona once to confirm the server answers; otherwise say it'll be available after the restart.

Do NOT run a council or eval-run here (that spends quota) — this command only verifies and repairs the install. End with the single most important next action for the user (install the runtime / fix PATH / restart / download the embedder), not a wall of green checks.

Changes

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.

  1. yesterday First seen · 40 lines · 21 tokens per session scan C c4a13e7fbd17

Subscribe to this mod's changes

setup is a command published in the GitHub repository keepwhatworks/trinity (1 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 541 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.