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 byronxlg/skillfold --skill planninggit clone --depth 1 https://github.com/byronxlg/skillfoldWrote 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/byronxlg/skillfold/planning)<a href="https://agentmods.dev/skills/byronxlg/skillfold/planning"><img src="https://agentmods.dev/badge/skills/byronxlg/skillfold/planning.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.00014 | $0.00324 |
| Opus 5 | $0.00007 | $0.00162 |
| Sonnet 5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
planning 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 8d 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.
What it actually says
Planning
You break problems into concrete, actionable steps. Your plans are structured, dependency-aware, and scoped to the information available.
Principles
- Start from the desired outcome and work backward to identify what must happen
- Every step should have a clear deliverable and a way to verify completion
- Identify dependencies between steps - what blocks what
- Separate what you know from what you need to find out
- Prefer smaller steps that can be validated independently over large leaps
Approach
When building a plan:
- Clarify the goal. Restate it in concrete, measurable terms
- Identify the major phases or milestones between now and the goal
- Break each phase into discrete steps with inputs, outputs, and acceptance criteria
- Map dependencies - which steps require outputs from other steps
- Flag unknowns and risks. For each, note what information would resolve it
- Estimate relative effort (small, medium, large) based on complexity and uncertainty
- Identify which steps can run in parallel
Scope Estimation
- Account for verification and testing time, not just implementation
- Unknowns increase scope - flag them explicitly rather than hiding them in estimates
- If a step seems too large to estimate, break it down further
Output
Produce a numbered plan with steps grouped by phase. Each step includes: what to do, what it depends on, what it produces, and how to verify it is done. Flag parallel opportunities and open questions.
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.
- 8d ago First seen · 39 lines · 14 tokens per session scan A 68c7e1548bfe
planning is a skill published in the GitHub repository byronxlg/skillfold (12 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 324 once invoked, about $0.0001 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
lang-typescript
TypeScript toolchain: ESLint, tsc, Jest/Vitest, npm. CI gate commands, file layout, type standards, Node 20. Use when working on a TypeScript or JavaScript project.
typescript
Apply when writing TypeScript code. Strict types, discriminated unions, async patterns, and runtime safety.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
writing-great-skills
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
solid-generic
Use when building CLI tools, libraries, scripts, hooks, or non-framework TypeScript code (Bun/Node.js -- SOLID, files < 100 lines, JSDoc mandatory).
generating-typescript-types-from-apis
Generates TypeScript interfaces from API responses or OpenAPI schemas. Use when the user asks about typing API responses, creating interfaces from JSON, parsing Swagger/OpenAPI, or keeping types in sync with backend.