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-export-openspecnpx skills add ijust/intent-planner --skill intent-export-openspecgit 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.00053 | $0.03804 |
| Opus 5 | $0.00026 | $0.01902 |
| Sonnet 5 | $0.00011 | $0.00761 |
| Haiku 4.5 | $0.00005 | $0.00380 |
Grade A, and why
intent-export-openspec 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
intent-export-openspec Skill
Core Mission
- Success Criteria:
- One target packet is converted into an OpenSpec proposal draft (Why/What Changes/Impact) + delta spec hints
- With the common contract, input is limited to the target packet +
selectedfrom the common selection result; only contract absence uses the existing packet + Compass path, and no full Tree/Compass is transcribed into OpenSpec - The delta hints carry parent intent / invariant references, forming a propagation structure to impl
- The output is led by natural-language guidance, and
/opsx:proposecan be invoked when instructed to proceed - The output is confined to
.intent/openspec/and does not touch.intent/cc-sdd/ - No application code has been changed at all
Execution Steps
Step 1: Narrow down to one target packet
- Read
.intent/packets/index.mdand present the active packet candidates. If index.md is absent, build the candidate list directly from the frontmatter of the files under.intent/packets/active/, continue, and prompt regeneration of the index. If.intent/packets/itself is absent (oractive/is empty), guide the user to "run/intent-packetsfirst" and stop. - If a packet is specified by argument, use it; otherwise narrow down to one from the candidates by priority or user confirmation, and read only the file of the confirmed target packet (under
.intent/packets/active/) — do not bulk-read all packet files. - Draft guard: when the confirmed target packet's
stateis draft, confirm via AskUserQuestion whether to "activate it and continue the export"; once the user approves, update the frontmatterstateto active and regenerateindex.mdbefore continuing (never export a draft as is without confirmation; this activation is the only canonical write the export makes). - 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, continue with the standard default and announce it.
What ships with it
3 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.
- 2d ago First seen · 107 lines · 53 tokens per session scan A bafdc1f39160
intent-export-openspec is a skill published in the GitHub repository ijust/intent-planner (5 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 3,804 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'.