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 skills add komluk/scaffolding --skill planning-methodologygit clone --depth 1 https://github.com/komluk/scaffoldingWrote 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/komluk/scaffolding/planning-methodology)<a href="https://agentmods.dev/skills/komluk/scaffolding/planning-methodology"><img src="https://agentmods.dev/badge/skills/komluk/scaffolding/planning-methodology.svg" alt="Measured on agentmods" 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.00051 | $0.00651 |
| Opus 5 | $0.00026 | $0.00326 |
| Sonnet 5 | $0.00010 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
planning-methodology 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 7d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Methodology Skill
Systematic approach for creating minimal, reversible implementation plans after research phase.
Auto-Invoke Triggers
- After ResearchPack is validated (score >= 80)
- Before code implementation begins
- When task requires multi-file changes
- User requests implementation plan
5-Step Methodology
Step 1: ResearchPack Review (30 sec)
- Verify ResearchPack score >= 80
- Extract required APIs and methods
- Note all gotchas and caveats
- List open questions
Step 2: Codebase Analysis (60 sec)
- Find existing patterns to follow
- Identify files to modify
- Check for similar implementations
- Map component dependencies
Step 3: Change Mapping (60 sec)
- List all files to modify/create
- Define minimal change set
- Identify dependencies between changes
- Plan test coverage
Step 4: Risk Assessment (30 sec)
- Identify potential failure points
- Assess impact on existing code
- Define rollback per change
- Flag breaking changes
Step 5: Plan Documentation (60 sec)
- Write structured ImplementationPlan
- Include verification per step
- Document rollback procedure
- Define success criteria
Output Format: ImplementationPlan
## ImplementationPlan: [Feature]
### Scope
- Files to modify: X
- New files: Y
- Tests to add: Z
### Changes
| # | File | Action | Verification |
|---|------|--------|--------------|
| 1 | path/file.ts | MODIFY | type-check |
| 2 | path/new.ts | CREATE | builds |
### Steps
1. [Step with verification]
2. [Step with verification]
### Rollback
[How to revert each change]
### Success Criteria
- [ ] npm run validate passes
- [ ] Feature works as specified
Planning Principles
Minimal Changes
- Only modify what's necessary
- No "while we're here" improvements
- Prefer small, focused changes
Reversibility
- Every change must be revertable
- Document rollback per step
- Keep backup strategy clear
Consistency
- Follow existing patterns
- Match naming conventions
- Use established architecture
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.
- 7d ago First seen · 113 lines · 51 tokens per session scan A 6796f199a732
planning-methodology is a skill published in the GitHub repository komluk/scaffolding (15 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 651 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
turnstile-loop-start
Starts a goal-directed loop run -- asks for mode, initialises state.json, then dispatches loop-runner repeatedly until the success condition is met, max-iterations is reached, or an unrecoverable error occurs.
turnstile-loop-status
Reads turnstile/loops/ /state.json and renders the current phase, status, and full iteration history in the terminal.
turnstile-brain-init
Opt-in bulk bootstrap of turnstile/code/ -- one linked note per source file. The default pipeline is lazy (code notes only for ticket-touched files, written when the ticket passes review); this is the eager exception. Dispatched by /turnstile:brain-init only.
turnstile-brain
Vault layout, the shared note format, and the check-the-brain-first mandate. Auto-loads whenever any turnstile skill starts new work or /turnstile:review is about to commit.
turnstile-conversate
Entry point for natural-language turnstile requests -- classifies the message against board state, then answers directly or invokes the one matching skill (brainstorm, quick, refine, spec, sprint-plan, work, review, breakdown, drop, systematic-debugger, code-reviewer).
turnstile-work
Implements one sprint ticket via TDD and the turnstile-coder agent, checking the brain first. Dispatched by /turnstile:work or conversate routing only.