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 fetch-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/fetch-plan)<a href="https://agentmods.dev/skills/kimgoetzke/coding-agent-configs/fetch-plan"><img src="https://agentmods.dev/badge/skills/kimgoetzke/coding-agent-configs/fetch-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/fetch-plan"><img src="https://agentmods.dev/badge/skills/kimgoetzke/coding-agent-configs/fetch-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.00043 | $0.00979 |
| Opus 5.5 | $0.00017 | $0.00392 |
| Sonnet 5.5 | $0.00009 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
fetch-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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fetch a Saved Plan
Use this skill to reopen an existing plan created with the planning-mode or planning skill.
Persistence
This skill belongs to the plans skill group. A persistence implementation decides where and how plans are stored. Before listing or opening plans, 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, lists its documents or reads a planning document.
A selected plan may contain these planning documents:
planprogressfindingsquestions
Phase 1: List plans only
- List plans; do not read any planning documents yet
- Sort plans newest first
- Show the plan names exactly as stored, in a numbered list
Example:
2026-03-20 refactor-auth-flow2026-03-18 add-retry-metrics
If no plans exist, tell the user no saved plans were found and suggest creating one with the planning-mode or planning skill.
If only a single plan exists, skip "Phase 2: Ask the user to choose" and consider this plan to be the one the user intends to select, then proceed to "Phase 3: Load the selected plan" and load this plan.
Phase 2: Ask the user to choose
Prompt the user to reply with either:
- the list number, or
- the plan name
Selection rules:
- If the input is a number, resolve it against the numbered list
- If the input is text, try exact plan-name match first
- If no exact match exists, allow a single unambiguous case-insensitive partial match
- If the input is invalid or ambiguous, explain why and ask again
- Do not read any plan documents before a valid selection is resolved
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 · +8 lines · -6 tokens per session a2ab949bfca1
- 1mo ago Changed · +2 lines 13a6c65f06ed
- 1mo ago First seen · 96 lines · 49 tokens per session scan A 33270510dba9
fetch-plan is a skill published in the GitHub repository kimgoetzke/coding-agent-configs (2 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 979 once invoked, about $0.0002 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…