Borrowing it
Nothing to install: this file belongs to nickmisasi/planner. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nickmisasi/planner/main/.claude/skills/export/SKILL.mdgit clone --depth 1 https://github.com/nickmisasi/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/nickmisasi/planner/export)<a href="https://agentmods.dev/skills/nickmisasi/planner/export"><img src="https://agentmods.dev/badge/skills/nickmisasi/planner/export/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/nickmisasi/planner/export"><img src="https://agentmods.dev/badge/skills/nickmisasi/planner/export.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.00030 | $0.00562 |
| Opus 5.5 | $0.00012 | $0.00225 |
| Sonnet 5.5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
export 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 2mo 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce a clean, shareable spec document from the current idea's spec.
Instructions
When the user invokes /export, follow these steps:
1. Ensure Context is Loaded
Read the current idea's spec.md, research.md, and assumptions.md. If no idea is active, trigger /continue first.
2. Generate the Export
Create a clean, self-contained Markdown document. The output should:
Header:
# <Idea Name>
**Author:** Nick Misasi
**Date:** <today's date>
**Status:** <current status>
**Project:** <project name>
Sections (in order):
- Background — Context the reader needs. Pull from spec.md Background section.
- Problem Statement — What we're solving. From spec.md.
- Proposal — High-level solution. From spec.md.
- Technical Details — Architecture, APIs, data models. From spec.md. Inline any critical research findings from research.md that support the technical choices.
- Milestones — Phases and task breakdowns. From spec.md.
- Open Questions — Remaining unknowns. From spec.md open questions + any unresolved assumptions from assumptions.md with confidence < 7.
- Out of Scope — What we're not doing. From spec.md.
- References — Links to relevant docs, repos, prior art. Compiled from spec.md and research.md.
Formatting rules:
- No internal repo references (no paths like
projects/foo/ideas/...) - No assumption confidence scores (those are internal)
- Professional tone, suitable for a Mattermost channel post
- Use clear headers and bullet points
- Include diagrams or code blocks where the spec has them
- Keep it concise — a spec, not a novel
3. Present the Export
Output the full generated document as a code block so the user can review it.
4. Ask About Delivery
Use AskUserQuestion to ask:
- Copy to clipboard — Just show it (already done above)
- Save to file — Write to
projects/<project>/ideas/<idea>/export.md - Both
5. Update Session
Use the CLI to note the export:
python3 bin/planning update-session \
--project <project-slug> \
--idea <idea-slug> \
--add-decision "Exported spec on <today's date>"
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.
- 2mo ago First seen · 62 lines · 30 tokens per session scan A d197f7854155
export is a skill published in the GitHub repository nickmisasi/planner (5 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 562 once invoked, about $0.0001 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.
export compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| exportnickmisasi/planner | Skill | 5 | 6mo ago | MIT | A | 30 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |