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/kimgoetzke/coding-agent-configs/planningnpx skills add kimgoetzke/coding-agent-configs --skill planninggit clone --depth 1 https://github.com/kimgoetzke/coding-agent-configsWrote 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/kimgoetzke/coding-agent-configs/planning)<a href="https://agentmods.dev/skills/kimgoetzke/coding-agent-configs/planning"><img src="https://agentmods.dev/badge/skills/kimgoetzke/coding-agent-configs/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 | $0.00024 | $0.01471 |
| Opus 5 | $0.00012 | $0.00736 |
| Sonnet 5 | $0.00005 | $0.00294 |
| Haiku 4.5 | $0.00002 | $0.00147 |
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 4d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning
Planning folder
- Any plan must be stored in
{repo root}/.ai/planning/{yyyy-mm-dd} {task-name}/- where:{repo root}is the root of the current repository{yyyy-mm-dd}is the date of the plan creation{task-name}is an extremely succinct name for the task in kebab-case
Planning files
Use persistent markdown files as your "working memory on disk." Context windows are volatile and limited; anything important gets written to disk.
- For any plan, you must create the following files in the plan folder:
- plan.md — Track work breakdown and progress
- questions.md — Track your questions and the user's responses and vice versa
- findings.md — Store research and discoveries
- For multi-phase plans, you must also create:
- progress.md — Session log and test results
- Before creating the planning files, you must read the starting templates in
./templates/ - You must use the starting templates when creating or updating planning files to guide the structure and content of these files
| File | Purpose | When to Update | Scope |
|---|---|---|---|
plan.md |
Work breakdown, decisions | After each phase | All plans |
findings.md |
Research, discoveries | Per 2-action rule | All plans |
questions.md |
Log of questions and user responses | Throughout planning | All plans |
progress.md |
Session log, test results | Throughout session | Multi-phase only |
Workflow
If you decide or are expected to produce a plan, follow the steps outlined in this section in order.
Step 1: Research & discover
- Gather requirements from the user's request
- Derive
{task-name}— an extremely succinct name for the task, use kebab-case e.g.refactor-mfa-flow - Create the plan folder and
findings.mdfollowing the template: templates/findings.md - Explore the codebase to understand the scope of the change
- Document findings in
findings.mdas you go
What ships with it
5 files 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.
- 4d ago First seen · 149 lines · 24 tokens per session scan A 8ef2dc1d4d89
planning is a skill published in the GitHub repository kimgoetzke/coding-agent-configs (2 stars, last pushed 15d ago), licensed MIT. It adds 24 tokens to every session and 1,471 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-31.
Other skills, from other repositories
codebase-memory
Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions…
using-pi-subagents
Operate pi-subagents jobs safely, including direct-work decisions, least-privilege tool selection, thinking-level selection, delegation, bidirectional messaging, parallel starts, timeout selection, waiting, cancellation, result handling, verification, and writer isolation.
skill-creator
Create or update Agent Skills (SKILL.md plus optional scripts, references, or assets). Use when someone asks to design a new Agent Skill, refine an existing one, or structure skills for Pi discovery, packaging, or other Agent Skills-compatible clients.
pi-ralph-wiggum
Long-running iterative development loops with pacing control and verifiable progress. Use when tasks require multiple iterations, many discrete steps, or periodic reflection with clear checkpoints; avoid for simple one-shot tasks or quick fixes.
accordion-context-folding
Read this skill if you see {# FOLDED} markers in your context (e.g. {#3f9a2c FOLDED}), or if earlier parts of your context look summarized. Accordion is a desktop tool that may compact older context blocks to keep you under a token budget. The unfold tool restores a folded block (open from your next turn); the recall…
accordion-context-recall
Read this skill when you need to read the full content of a folded context block RIGHT NOW as a tool result — without opening it in your standing context. Use recall(codes) when you only need a value once and do not want to permanently restore the block. Accordion may fold older parts of your context to keep token…