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/hazat/pi-config/plannpx skills add HazAT/pi-config --skill plangit clone --depth 1 https://github.com/HazAT/pi-configWrote 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/hazat/pi-config/plan)<a href="https://agentmods.dev/skills/hazat/pi-config/plan"><img src="https://agentmods.dev/badge/skills/hazat/pi-config/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.00034 | $0.00461 |
| Opus 5 | $0.00017 | $0.00230 |
| Sonnet 5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
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 5d 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
Plan
Plan in the current chat. Do not implement, create todos, review, or launch source-writing agents.
Workflow
- Investigate: inspect repository instructions, Git state, relevant files, tests, and existing patterns. Ground claims in what you read.
- Confirm intent: summarize the requested outcome, implicit requirements, boundaries, and the most important success condition. Ask for corrections.
- Clarify: ask only questions whose answers materially change the design. Resolve observable behavior, edge cases, quality level, and explicit exclusions.
- Compare approaches: present 2–3 materially different options with tradeoffs, risks, effort, and a recommendation.
- Select: ask the user to choose or approve an approach. Do not write the plan before this checkpoint.
- Write: after selection, resolve routine details from evidence and write only the absolute plan path supplied by the caller. Stop.
Keep each interactive turn focused. Investigate facts instead of asking the user to provide facts available in the checkout.
Plan Format
# [Plan name]
**Status:** Ready
**Request:** [one sentence]
**Selected approach:** [one sentence]
## Intent
## Scope
### In scope
- ...
### Out of scope
- ...
## Acceptance Criteria
- [ ] ISC-1: [binary, observable criterion]
- [ ] ISC-2: ...
## Repository Evidence
- `path:line` — [relevant fact or convention]
## Approaches Considered
### Selected: [name]
[Why it best fits]
### Rejected: [name]
[Tradeoff that ruled it out]
## Implementation
1. [ordered change with files/components]
## Verification
- `[command]` — [what it proves]
## Assumptions and Risks
- [assumption or failure mode] — [mitigation or accepted risk]
Use objective acceptance criteria and name important wrong approaches. Do not create a sidecar directory, run record, todo file, review file, or custom state.
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.
- 5d ago First seen · 66 lines · 34 tokens per session scan A 9216380c04e5
plan is a skill published in the GitHub repository HazAT/pi-config (443 stars, last pushed 10d ago), licensed MIT. It adds 34 tokens to every session and 461 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…