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-export-openspecgit 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-export-openspec)<a href="https://agentmods.dev/skills/ijust/intent-planner/intent-export-openspec"><img src="https://agentmods.dev/badge/skills/ijust/intent-planner/intent-export-openspec/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-export-openspec"><img src="https://agentmods.dev/badge/skills/ijust/intent-planner/intent-export-openspec.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.00053 | $0.04109 |
| Opus 5.5 | $0.00021 | $0.01644 |
| Sonnet 5.5 | $0.00011 | $0.00822 |
| Haiku 4.5 | $0.00005 | $0.00411 |
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 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 — 112 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
For acceptance material, the limited input also includes original requirements, approved changes, and relevant journey passages explicitly referenced by the target packet. The packet-and-selected-only limits and ban on Tree-body transcription below allow this exception for reading and summarizing target conditions. Carry needed conditions into the existing acceptance material without reading unrelated full documents or other packets. Do not add this material to constraint-selection sources, candidates, selected, downstream project-wide constraints, or the internal selection record.
- Apply “Assignment selection and continuation” in
.intent/execution-contract.mdbefore target selection. Continue the agreed target; an explicit export target alone does not reassign implementation. If the contract is absent, recover the conversational target and ask if unknown rather than falling back to the latest export.
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. - Use an explicit packet argument for this export operation. On continuation without an argument, retain the conversationally agreed target. Only if the target cannot be recovered, present candidates, ask the user, and wait for the answer. Read only the confirmed target packet under
.intent/packets/active/; do not bulk-read packet bodies. - 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.
- 1mo ago Changed · +5 lines eded05dbe679
- 2mo 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 1mo ago), licensed MIT. It adds 53 tokens to every session and 4,109 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…