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/flinedev/plankit/donenpx skills add FlineDev/PlanKit --skill donegit clone --depth 1 https://github.com/FlineDev/PlanKitWhat 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.00058 | $0.01400 |
| Opus 5 | $0.00029 | $0.00700 |
| Sonnet 5 | $0.00012 | $0.00280 |
| Haiku 4.5 | $0.00006 | $0.00140 |
Grade A, and why
done 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Done
Archive completed work to Done.md and browse past accomplishments.
Config Preamble
Before any operation, locate the PlanKit folder and read its config:
- Check if
PlanKit/exists in the project root. If not, checkplan-kit/. - Read
.config.jsonfrom the PlanKit folder to get the naming convention.
Determine file path:
- Done:
PlanKit/Done.mdorplan-kit/done.md
If Done.md doesn't exist, create it with just # Done as content.
Archive Scenarios
Other PlanKit skills trigger these scenarios by loading this skill and specifying which one applies. When loaded, find the matching scenario and follow its instructions.
Scenario 1: Mission Completed (or Dropped)
Triggered by the mission-breakdown skill after a mission file is deleted.
Input from calling skill: mission name, mission letter, feature name, feature number, file path, status (✅ completed or 🛑 dropped), reason (for dropped only), PR numbers (if known).
- Get the deletion commit SHA:
git log -1 --format=%h -- "path/to/deleted/file"- This finds the commit that last touched the file (the deletion commit)
- Read Done.md
- Find or create the version section:
- Look for
## vX.Ymatching the feature's roadmap version - If it doesn't exist, create it:
## vX.Y — Subtitle (YYYY-MM-DD →) - Start date = today if this is the first entry for this version
- End date left blank (filled when version is released)
- Look for
- Find or create the feature subsection:
- Look for
### ... NNN-FeatureNameunder the version section - If it doesn't exist, create it with the feature's one-line description from the Roadmap
- Don't set the feature-level status marker yet (it's set when the feature is fully complete)
- Look for
- Add the mission line:
- Format:
- ✅ X-MissionName · plan: \SHA`` (for completed) - Format:
- 🛑 X-MissionName · plan: \SHA` — reason` (for dropped) - Append
· PR #Nif PR numbers were provided
- Format:
- Write Done.md
What ships with it
1 file 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 · 119 lines · 58 tokens per session scan A 2e8126d20373
done is a skill published in the GitHub repository FlineDev/PlanKit (20 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 1,400 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-30.
Other skills, from other repositories
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
organize-project
Organise documents into folders and move them between folders and modules with MOVE. Use when a module has grown unstructured, when restructuring a project, or when a document is in the wrong place.
smithers-supervise
Watch for stale running runs and auto-resume them. Run smithers supervise --help for usage details.