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/resumegit 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.00025 | $0.01401 |
| Opus 5 | $0.00013 | $0.00700 |
| Sonnet 5 | $0.00005 | $0.00280 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade B, and why
resume scanned grade B 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
If the user `cd`'d into the build folder itself, `.claude/builds/` won't resolve — they should be at the **project root** (where `.claude/` lives). If you can't find `.claude/builds/`, say so and ask for the project root How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/compass:resume
Continue a Compass build that was paused or interrupted. State is on disk, so closing the terminal loses nothing.
Orientation first (v0.28.0, INV-ORIENT)
Run compass.sh orient and show its output before anything else — the same renderer the other two front doors use, so all three show an identical, consistent picture instead of three hand-written variants that drift apart (INV-ONE-RENDERER). The UserPromptSubmit hook usually paints it before this command starts; run it explicitly if it did not.
Procedure
- Identify the build WITHOUT trusting the global
CURRENT(a stale/ambiguousCURRENTis what resumed the wrong build before — so it is only a last-resort hint, never the disambiguator):- In a build's worktree? If
git rev-parse --show-toplevelends in*.compass/<slug>(or the branch iscompass/<slug>), THAT is the build. The cwd identifies it unambiguously — use it. - Otherwise run
compass.sh active-builds: 0 → nothing in-flight, but if.claude/builds/PROGRAM.mdexists, runcompass.sh program-ledger <program>(surface any FLAG first — M15) thencompass.sh program-next <program>and offer to start the next phase if one exists (else nothing to resume); 1 → resume it; >1 → REFUSE to guess — list them and require/compass:resume <slug>. Only if exactly one is active and the user gave no slug may you fall back to theCURRENThint. - Resolve state paths via
compass.sh state-root(so this works from inside a worktree too).
- In a build's worktree? If
- Read that build's
receipts.md,progress.md, and — if building —plan.md. Disambiguate the stage:- The last PASS receipt tells you the last completed stage. A
build · IN-PROGRESS · step k/nreceipt (or an absent build receipt with someplan.mdboxes checked) means the build is mid-flight, not done — resume at the first unchecked step. An absent build receipt with zero boxes checked means build never started. plan.mdcheckboxes are authoritative for build progress; ifprogress.mddisagrees, trust the checkboxes.progress.mdstatus qualifies the stage (contract-LOCKEDvsplan-LOCKED,in-review (Rn), etc.).- Read
contract.md(the invariant) andreview-ledger.md(open issues). - Intake (v0.13.0): status
intake (phase N)means the contract interview is mid-flight — runcompass.sh intake-phase <dir>for the highest completed phase and re-enter the contract skill's Intake Protocol at the next phase (intake.md is append-only truth; an in-flight question is simply re-asked). - Post-ship loop (v0.12.0): status
post-ship (round k/cap)means SHIPPED-but-not-final — the post-ship critique loop is open. Re-enter the ship skill's loop at the first round WITHOUT aloop.logregistration (loop.logis the truth; a round receipt without a matching log line means that round must RE-RUN).compass.sh loop-converged <dir> postshiptells you exactly where the loop stands.
- The last PASS receipt tells you the last completed stage. A
- PUSH the cockpit first (INV-PUSH-RESUME). Run
compass.sh cockpit <state-root>/<slug>and show it — the two-altitude view (program phases + contracts if any, above the current build's 7-stage strip + step k/n + next) — so a fresh-terminal resume shows where things stand with zero further typing. THEN state in ONE line where things stand — e.g. "Resuming — plan-LOCKED, building step 4/11 (next: the reconciliation query)." Do not recite the files. - Re-bind ownership to THIS session before handing off:
compass.sh own <slug> --session "$CLAUDE_CODE_SESSION_ID". The build's Stop-hook guard now follows the live (resuming) session — an orphaned build (its old terminal closed) is silent until this re-bind restores the guard (v0.9.0). - Continue from the recorded next action, handing back to the right stage skill (
compass:build,compass:review-build, etc.) and back into the orchestrator's gate flow.
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.
- 2d ago First seen · 40 lines · 25 tokens per session scan B f2b810b5a233
resume is a command published in the GitHub repository Rishi4792/compass (2 stars, last pushed 8d ago), licensed MIT. It adds 25 tokens to every session and 1,401 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.