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/nickmisasi/planner/exportnpx skills add nickmisasi/planner --skill exportgit clone --depth 1 https://github.com/nickmisasi/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.00030 | $0.00562 |
| Opus 5 | $0.00015 | $0.00281 |
| Sonnet 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 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 — 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.
- 2d 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 4mo ago), licensed MIT. It adds 30 tokens to every session and 562 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…