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-from-codenpx skills add ijust/intent-planner --skill intent-from-codegit 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.00064 | $0.03633 |
| Opus 5 | $0.00032 | $0.01817 |
| Sonnet 5 | $0.00013 | $0.00727 |
| Haiku 4.5 | $0.00006 | $0.00363 |
Grade A, and why
intent-from-code 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
intent-from-code Skill
Core Mission
- Success Criteria (success if achieved; the scope-fixing / extraction / sensitive-info protection / recap procedure detail is consolidated into Execution Steps and the four rules, and only the outcomes are declared here):
- Reads the user-specified scope of existing code read-only and extracts intent candidates (roughly L0–L3), invariant candidates, and gaps of silence (places the code demonstrates but where no description of intent exists), writing them all out to
.intent/code-ingest/code-ingest.mdwith an inferred marker and a recovery basis (Step 1–3. R1.1) - Writes by full replacement only after all extraction is complete, so the same input yields the same output on re-run, without mixing old extractions with new ones (Step 3. R1.2)
- Governs the reading scope: requires the scope to be specified, and even when it is unspecified does not fall back to scanning the whole repository but proposes a recommended scope and asks for confirmation, never using anything outside the fixed scope as extraction input (delegated to read-scope. R2.1 / R2.4)
- When the scope is empty or does not exist, does not stop but states explicitly that "there is no readable material," and ends with an empty candidate list without filling in by guessing (fail-open. R2.3)
- At the end of the output, guides that "the user promotes approved items by copying them by hand into the discover / compass dialogue," and holds no machine handoff that auto-launches discover / compass from the skill (delegated to recap-and-promotion. R1.4 / R4.4)
- Limits writes to under
.intent/code-ingest/, and never modifies canonical (intent-tree / intent-compass / packets), application code, target code, or the existing documents used as input (read-only. Canonical byte content is unchanged before and after execution. R4.1) - Keeps interpretation and candidate formation with the LLM; if an optional local read-only analysis or index is used, limits it to structural observation and recovery-basis collection and does not confirm intent from its output alone; falls back to direct code reading when analysis is unavailable, uninitialized, stale, or insufficient
- Reads the user-specified scope of existing code read-only and extracts intent candidates (roughly L0–L3), invariant candidates, and gaps of silence (places the code demonstrates but where no description of intent exists), writing them all out to
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.
- yesterday First seen · 73 lines · 64 tokens per session scan A 9cc7702a5d87
intent-from-code is a skill published in the GitHub repository ijust/intent-planner (5 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 3,633 once invoked, about $0.0003 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'.