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/endlessblink/master-plan/donenpx skills add endlessblink/master-plan --skill donegit clone --depth 1 https://github.com/endlessblink/master-planWhat 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.00052 | $0.01239 |
| Opus 5 | $0.00026 | $0.00620 |
| Sonnet 5 | $0.00010 | $0.00248 |
| Haiku 4.5 | $0.00005 | $0.00124 |
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 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Completion Workflow
Finalize a completed task: verify tests pass, commit changes, update MASTER_PLAN.md, and push.
Triggers
/master-plan:done- Main command- "mark done", "task complete", "finish task", "ship it"
Workflow
Step 1: Check What Changed
Run git status to see what files were modified:
git status
git diff --stat
Output immediately:
Files changed:
- [list of modified files]
Step 2: Get Task Information
Use AskUserQuestion to collect:
-
Task ID (header: "Task ID")
- Options: "Tracked task (enter ID)" or "Quick fix (no task ID)"
-
Run tests? (header: "Tests")
- Options: "Yes — run test suite (Recommended)" or "Skip tests"
Then ask in plain text: "What's a brief summary of the changes? (1-2 sentences)"
IMPORTANT: Wait for user to provide the summary before proceeding.
Step 3: Run Tests (unless skipped)
Detect and run the project's test command. Check in order:
- If
package.jsonexists →npm test - If
Cargo.tomlexists →cargo test - If
pyproject.tomlorsetup.pyexists →pytest - If
Makefilewithtesttarget →make test - If
go.modexists →go test ./...
If tests fail: STOP immediately. Report failures. Do NOT proceed. If tests pass: Continue. If no test command found: Warn user and continue.
Step 4: Update MASTER_PLAN.md (if tracked task)
Skip this step if user selected "Quick fix (no task ID)".
CRITICAL: Tasks may appear in multiple locations. Update ALL of them:
4a. Summary/Roadmap Table
Find the task row and update:
# Before:
| **TASK-XXX** | **Title** | **P2** | PLANNED | ... |
# After:
| ~~**TASK-XXX**~~ | ✅ **Title** | **P2** | ✅ DONE (YYYY-MM-DD) | ... |
4b. Subtask/Bullet Lists
# Before:
- TASK-XXX: Description
# After:
- ~~TASK-XXX~~: ✅ Description
4c. Detailed Section Header
# Before:
### TASK-XXX: Title (IN PROGRESS)
# After:
### ~~TASK-XXX~~: Title (✅ DONE)
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 · 184 lines · 52 tokens per session scan A 66c20d15a772
done is a skill published in the GitHub repository endlessblink/master-plan (27 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 1,239 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
flow-next-work
Execute a flow-next spec or task end-to-end with worker subagents, gates, and commits. Use when asked to work on, implement, or execute fn-N.
trellis-finish-work
Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.
kn-commit
Use when committing code changes with proper conventional commit format and verification.
campaign-commit
Choose the correct commit command in a campaign workspace. Use when you are about to commit and need to select camp commit, camp p commit, fest commit, or intentional root pointer sync via camp refs-sync.
commit-work
Verify, stage, and commit a reviewed Codument work step with a focused conventional commit.
walk-commits
Side-route skill for an interactive, commit-by-commit comprehension walkthrough of a finished branch before merge. Use when the person about to merge didn't author the diff — or hasn't internalized it — and needs to understand each commit's intent, riskiest line, deliberate oddities, and what's absent by design, with…