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 kimgoetzke/coding-agent-configs --skill improve-a-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/improve-a-plan)<a href="https://agentmods.dev/skills/kimgoetzke/coding-agent-configs/improve-a-plan"><img src="https://agentmods.dev/badge/skills/kimgoetzke/coding-agent-configs/improve-a-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kimgoetzke/coding-agent-configs/improve-a-plan"><img src="https://agentmods.dev/badge/skills/kimgoetzke/coding-agent-configs/improve-a-plan.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.01058 |
| Opus 5.5 | $0.00014 | $0.00423 |
| Sonnet 5.5 | $0.00007 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
improve-a-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 2d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persistence
This skill belongs to the plans skill group. A persistence implementation decides where and how plans are stored. Before locating the plan, find the setting:
R="$(git rev-parse --show-toplevel 2>/dev/null)/.ai/config.properties"; { cat "$R" ~/.ai/config.properties | grep '^persistence\.plans[[:space:]]*=[[:space:]]*[^[:space:]]'; cat "$R" ~/.ai/config.properties | grep '^persistence[[:space:]]*=[[:space:]]*[^[:space:]]'; } 2>/dev/null | head -1 | tr -d ' \t\r'
- No output: use
local-ai-folder-markdown, the default for this skill group persistence.plans={value}orpersistence={value}: use{value}. If../planning/persistence/{value}.mddoes not exist, tell the user theplansskill group has no{value}implementation and uselocal-ai-folder-markdown
Read ../planning/persistence/{implementation}.md and follow it whenever this skill lists or opens a plan, or reads, writes or updates a planning document.
Phase 1: Locate the plan
Resolve the target plan using the first matching strategy:
- Context inference — check your conversation context for a plan location from a prior
planning-modeorplanningskill invocation in this session. If found, use it directly and confirm with the user (e.g. "Improving 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 an argument, resolve it as a number or plan name against the listed plans e.g.
2026-01-20 improve-mfa-flow. Do not read any plan documents until the plan has been resolved. - Single plan — if only one plan exists, select it automatically.
- Multiple plans — list plans newest first in a numbered list and ask the user to choose. Do not read any plan documents until the plan has been resolved.
- No plans — tell the user no plans were found and suggest creating one with the
planning-modeorplanningskill.
Phase 2: Improve the plan
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.
- 2d ago Changed · +13 lines e061383b9404
- 1mo ago First seen · 54 lines · 34 tokens per session scan A a34636a9d243
improve-a-plan is a skill published in the GitHub repository kimgoetzke/coding-agent-configs (2 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 1,058 once invoked, about $0.0001 per session on Opus 5.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
using-pi-subagents
Operate pi-subagents jobs safely, including direct-work decisions, least-privilege tools and attachments, thinking levels, delegation, bidirectional messaging, parallel starts, timeouts, waiting, cancellation, result handling, verification, and writer isolation.
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…
configure-pi-starship
Configure @narumitw/pi-starship and answer questions about its pi-starship.toml settings. Use when the user asks to create, edit, repair, migrate, or understand pi-starship.toml, or asks which pi-starship module, variable, option, style, palette, preset, or runtime behavior to use. Do not use for generic TOML, shell…
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.
typesafe-ai
Build AI-powered software with TypeSafe and Jev, or use pi-typesafe's typesafequestion tool for typed semantic judgments and probabilities. Use when a feature needs programmable common sense, when an LLM prompt-and-parse step could become a structured decision, or when designing, calling, evaluating, or…