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/update-plannpx skills add kimgoetzke/coding-agent-configs --skill update-plangit 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/update-plan)<a href="https://agentmods.dev/skills/kimgoetzke/coding-agent-configs/update-plan"><img src="https://agentmods.dev/badge/skills/kimgoetzke/coding-agent-configs/update-plan.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.00070 | $0.01810 |
| Opus 5 | $0.00035 | $0.00905 |
| Sonnet 5 | $0.00014 | $0.00362 |
| Haiku 4.5 | $0.00007 | $0.00181 |
Grade A, and why
update-plan 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Plan from User Responses
Process user responses in questions.md and update all related planning documents accordingly.
Prerequisites
- A plan must already exist under
{repo root}/.ai/planning/created by theplanningorplanning-modeskills - For default (non-
ask) mode: the plan'squestions.mdmust contain at least one question with a non-empty### Responsesection - For
askmode: the plan'squestions.mdmust contain at least one unprocessed question (with or without a response)
Argument parsing
The skill takes a single optional argument:
- If the argument is the literal string
ask(case-insensitive, trimmed) → enable ask mode and locate the plan via the Phase 1 strategies below (folder is not specified separately). - If the argument is anything else → treat it as a folder name (existing behaviour).
- If the argument is empty → no mode flag and no folder; fall through to the Phase 1 strategies.
ask is standalone — it cannot be combined with a folder name on the same invocation. If the user needs ask mode against a specific plan in a multi-plan repo, the Phase 1 multi-plan prompt will let them choose.
Throughout the rest of this skill, ask mode refers specifically to the case where the argument was ask.
Phase 1: Locate the plan
Resolve the target plan using the first matching strategy:
- Context inference — check your conversation context for a plan folder path from a prior
planning-mode/planningskill invocation in this session. If found, use it directly and confirm with the user (e.g. "Updating plan2026-03-24 auth refactor— correct?"). Proceed on confirmation; if the user says no, fall through to the next strategy. - User argument — if the user provided a non-
askargument, resolve it as a folder name against folders inside{repo root}/.ai/planning/. (Theaskkeyword is a mode flag, not a folder name — see "Argument parsing" above.) - Single plan — if only one plan folder exists, select it automatically.
- Multiple plans — list folders newest first in a numbered list and ask the user to choose.
- No plans — tell the user no plans were found and suggest creating one with the
planning-modeorplanningskills.
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 · 124 lines · 70 tokens per session scan A 04cf315b1b29
update-plan is a skill published in the GitHub repository kimgoetzke/coding-agent-configs (2 stars, last pushed 15d ago), licensed MIT. It adds 70 tokens to every session and 1,810 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-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…