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 skills add ijust/intent-planner --skill intent-compassgit clone --depth 1 https://github.com/ijust/intent-plannerWrote 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/skills/ijust/intent-planner/intent-compass)<a href="https://agentmods.dev/skills/ijust/intent-planner/intent-compass"><img src="https://agentmods.dev/badge/skills/ijust/intent-planner/intent-compass/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/skills/ijust/intent-planner/intent-compass"><img src="https://agentmods.dev/badge/skills/ijust/intent-planner/intent-compass.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.00043 | $0.02311 |
| Opus 5.5 | $0.00017 | $0.00924 |
| Sonnet 5.5 | $0.00009 | $0.00462 |
| Haiku 4.5 | $0.00004 | $0.00231 |
Grade A, and why
intent-compass 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
intent-compass Skill
Core Mission
- Success Criteria:
- North Star / Current Drift / Direction / Anti-direction / Invariants / Decision Rules / Evidence / Open Questions are all present
- The local optimizations Claude tends to make are explicitly enumerated in Anti-direction
- Only project-universal invariants are kept in the compass; packet-specific invariants are canonical in the packet file (Safety / Invariants)
- No application code has been changed at all
When addressing responsibility/dependency boundaries, read “Compare boundaries” in ../intent-packets/rules/design-boundaries.md before recording decisions. Do not auto-adopt options.
Execution Steps
Step 1: Read the prerequisites
- Read
.intent/intent-tree.md. If absent, guide the user to "run/intent-discoverfirst" and stop. Read the skeleton (L0–L4) from the body; read case records (機能追記/機能撤去/履歴/再起案) via the split store.intent/tree/—index.md→ the relevant<feature>.md— if it exists, otherwise from the legacy form at the body tail (permanent fallback; tree-normalize / DR133). - While reading, when you see an unsettled verb slipped into the settled phrasing of the compass / intent-tree (assume / reuse / planned / TBD / tentative, etc.), do not fix it by guessing; present it as a conversion proposal into Open Questions or an undetermined slot (with the reason and the revisit condition (Revisit when)). Promotion to a fixed value is left to the user's confirmation. Do not re-convert spots already recorded in Open Questions / Deferred / an undetermined slot.
- Read the mode state in order: the inherited issue directory's
discovery/<slug>-<rand>/mode.md(A34; inherit the issue name that discover output) → else the single.intent/mode.local.md(legacy) → else old.intent/mode.md(the CONTRACT.md read fallback contract). If both are absent, default to standard and add "mode undetermined;/intent-discoverrecommended" to the Open Questions (do not stop). - If an existing
.intent/intent-compass.mdexists, read it. If the split store.intent/compass/(one symbol = one file; INV80) has the symbol, readindex.md→ that file's## Lawfirst; for symbols not in the store, read the legacy body as before (the legacy path is a permanent fallback = DR133).
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +2 lines f0ee6f291fdf
- 2mo ago First seen · 72 lines · 43 tokens per session scan A ea3fc0cbd625
intent-compass is a skill published in the GitHub repository ijust/intent-planner (5 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 2,311 once invoked, about $0.0002 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 skills, from other repositories
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
orchestration-team
Use when coordinating assignments, selected review boundaries, or blocked work across a rig.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…