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 skills/ijust/intent-planner/intent-overviewnpx skills add ijust/intent-planner --skill intent-overviewgit clone --depth 1 https://github.com/ijust/intent-plannerWhat 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.00042 | $0.05084 |
| Opus 5 | $0.00021 | $0.02542 |
| Sonnet 5 | $0.00008 | $0.01017 |
| Haiku 4.5 | $0.00004 | $0.00508 |
Grade A, and why
intent-overview 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 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.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
intent-overview Skill
writes are limited to under .intent/overview/. Canonical .intent/*.md files are read-only, and generated output is derived.
Core Mission
- Success Criteria:
- Reads the existing scattered
.intent/artifacts (intent-tree / intent-compass / packets index & active / packets/plan / export-log / deltas / mode / drift-log) read-only, and generates a formatted overview view that humans and agents can read through at once at.intent/overview/overview.md(R1.1) - On re-run, regenerates the overview from the latest artifacts by full replacement, producing no duplication of the source of truth (idempotent regeneration. R1.3)
- When
.intent/or a required artifact (e.g. intent-tree) is absent, writes nothing, states the absence explicitly, and guides the user to the skill to run first (e.g./intent-discover) (R1.4) - Makes clear that the output is derived / regenerable / not the source of truth (and Git-untracked) (the reader's concern takes priority, so this may be relegated to the end of the view. R1.5)
- Organizes the whole picture into concern-separated derived views (intent view / dependency-block view / progress view), reflecting progress not as a single percentage but along axes of differing nature
- When the user asks in natural language for an "understanding map", "pre-start briefing", or "understanding gap sorting", generates
.intent/overview/agent-understanding-map.md/.intent/overview/active-packet-briefing.md/.intent/overview/understanding-gaps.mdas derived views, without writing to any canonical.intent/*.md - After the three separate readings and at most one human decision candidate at the top, lays out all packets as a single progress rail with the five signals +
[current stage → next stage(s) to pass through](read-only, without computing or inferring state) - Aggregates while keeping canonical intent distinct from inferred intent, and design intent distinct from implementation reality; marks gaps and unobserved areas as "unfilled / unobserved" and never fills them in by guessing
- Does not call other skills directly; coordinates only via read-only access to scaffold files (
.intent/*.md) and guidance in the output text (R6.5). Has no state machine / autonomous loop / resident process, and maintains zero external dependencies (R6.1 / R6.2)
- Reads the existing scattered
What ships with it
10 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.
- rules/aggregate-sources.md 9.9 KB
- rules/assignment-view.md 6.1 KB
- rules/coverage-map.md 4.9 KB
- rules/decision-inbox.md 5.6 KB
- rules/gap-readout.md 5.6 KB
- rules/mermaid-tree.md 8.4 KB
- rules/mermaid-views.md 7.5 KB
- rules/newcomer-onboarding.md 6.3 KB
- rules/progress-readout.md 20 KB
- rules/roadmap-projection.md 6.6 KB
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 · 93 lines · 42 tokens per session scan A c1d464765152
intent-overview is a skill published in the GitHub repository ijust/intent-planner (5 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 5,084 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 skills, from other repositories
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
office-hours
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to…
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
echo
Use when the user references past sessions, asks 'what did we do', 'do you remember', 'last session', 'recall', or 'continue from'.