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.
npx agentmods add commands/rishi4792/compass/gogit clone --depth 1 https://github.com/Rishi4792/compassWhat 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 | $0.00048 | $0.01363 |
| Opus 5 | $0.00024 | $0.00681 |
| Sonnet 5 | $0.00010 | $0.00273 |
| Haiku 4.5 | $0.00005 | $0.00136 |
Grade A, and why
go 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/compass:go — the front door
This is the single entry point for Compass. You don't need to remember the stage commands — /compass:go reads the current state and asks you where to go, every time.
The orientation block is rendered by a script, not written here — compass.sh orient. It picks the right block from your actual state: the mental model when nothing is in flight, a where-you-are block when a build is running. A UserPromptSubmit hook prints it before this command even starts, so you see it with zero typing.
This file deliberately contains no copy of that text. From v0.15.0 to v0.27.0 the welcome lived here as prose with a "print it" instruction nowhere, and its only tests grepped this file for the words — so it passed for twelve versions while printing 0 times in 30 real /compass:go invocations. One renderer, one source, behaviour-tested (INV-ONE-RENDERER, INV-ORIENT-DELIVERED).
What to do when invoked
-
Orientation first (INV-ORIENT). The hook normally paints it already. If it did not (hook disabled,
COMPASS_QUIET, an older install), runcompass.sh orientand show its output before anything else. Never retype the block from memory — one renderer, three doors. -
Read the build state (never guess it):
-
compass.sh state-root→ the.claude/buildsdir. -
.claude/builds/CURRENT→ the last-active slug hint ·.claude/builds/INDEX→ every build (slug · goal · status · facets · touches) · the active build's.claude/builds/<slug>/progress.md→ the authoritative status + Stage + Next. -
compass.sh builds(oractive-builds) → the in-flight (non-terminal) builds. -
PUSH the cockpit immediately (INV-PUSH-RESUME). As soon as an in-flight build is identified, run
compass.sh cockpit <state-root>/<slug>and show it FIRST — the two-altitude view (program phases + contracts, if any, above the current build's stage + step k/n + next) — so a returning user (incl. a fresh terminal) sees exactly where they are with zero further typing, before any menu.
-
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.
- yesterday First seen · 41 lines · 48 tokens per session scan A 5c9a8486689e
go is a command published in the GitHub repository Rishi4792/compass (2 stars, last pushed 8d ago), licensed MIT. It adds 48 tokens to every session and 1,363 once invoked, about $0.0002 per session on Opus 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.