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/milestonenpx skills add nickmisasi/planner --skill milestonegit 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.00000 | $0.02121 |
| Opus 5 | $0.00000 | $0.01060 |
| Sonnet 5 | $0.00000 | $0.00424 |
| Haiku 4.5 | $0.00000 | $0.00212 |
Grade A, and why
milestone 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 3d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: milestone
description: Complete the current work as a milestone and start fresh for the next phase. Archives current idea files, including IMPL_ORCHESTRATION_PLAN.md when present, closes out affected worktrees with final local commits, archives repo-local .planning/PLAN.md files into milestone folders, writes a summary, and resets working files. Use when the user wants to mark a phase of work as done and move to the next.
Complete the current work on an idea as a milestone. Archive all current planning files (spec, research, assumptions, session, spikes, and IMPL_ORCHESTRATION_PLAN.md if present) into a milestone folder, close out affected implementation worktrees with final local commits, archive repo-local .planning/PLAN.md files into milestone folders inside each worktree, write a summary, and reset working files so the next phase starts clean — while preserving full historical context.
Instructions
When the user invokes /milestone, follow these steps:
1. Ensure Context is Loaded
If you haven't already loaded the current idea's files, read them now:
spec.mdsession.mdassumptions.mdresearch.mdIMPL_ORCHESTRATION_PLAN.md(if it exists)MILESTONES.md(if it exists — this means prior milestones already exist)
If no idea is currently active, trigger the /continue skill first to select one.
2. Draft the Milestone Summary
Before archiving, synthesize the current state into a milestone summary. Read session.md and spec.md to draft:
- Milestone name: A short descriptive name (e.g., "POC Validation", "Core API Implementation")
- Slug: URL-safe version (e.g., "poc-validation", "core-api")
- Summary: 2-4 sentences capturing what was accomplished
- Outcome: One of
completed,partial, orpivoted - Key outcomes: Bullet list of concrete deliverables or validations
- Key decisions: Carried from session.md
- What carries forward: What context/decisions/constraints feed into the next milestone
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.
- 3d ago First seen · 180 lines · 0 tokens per session scan A bd0d306807bb
milestone is a skill published in the GitHub repository nickmisasi/planner (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,121 tokens. 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.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…