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 HazAT/pi-config --skill write-todosgit 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/write-todos)<a href="https://agentmods.dev/skills/hazat/pi-config/write-todos"><img src="https://agentmods.dev/badge/skills/hazat/pi-config/write-todos.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00467 |
| Opus 5 | $0.00018 | $0.00234 |
| Sonnet 5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
write-todos 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 8d 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
Write Todos
Read the absolute plan path supplied by the caller. Write only the supplied todos path; do not implement work or launch agents.
Rules
- Preserve the plan's architecture, scope, exclusions, and acceptance criteria.
- Use stable sequential IDs (
TODO-001,TODO-002, ...). When updating an existing file, preserve IDs and completed evidence. - Make each source-writing todo fit one focused worker and one commit.
- Source-writing todos must be dependency ordered because workers share one checkout and run sequentially.
- Repeat the constraints a worker needs; do not make it infer critical intent.
- Name target files, useful source references, objective checks, and plausible wrong approaches.
- Only the coordinator updates status, owner, commit, verification, and result fields. Delegated agents read this file but never edit it.
File Format
# Execution Todos
**Status:** Pending | In Progress | Complete | Blocked
**Plan:** `/absolute/path/to/session.plan.md`
**Updated:** [ISO-8601 timestamp]
## TODO-001 — [outcome]
**Status:** Pending | In Progress | Complete | Blocked
**Depends on:** none | TODO-NNN
**Owner:** unassigned | [SC label]
**Commit:** pending | [full SHA] | n/a
### Outcome
[What this produces and why]
### Constraints
- [plan decision to preserve]
- [explicit non-goal or wrong approach]
### Files and References
- `path/to/file` — [expected change]
- `path/to/example:line` — [pattern to follow]
### Acceptance Criteria
- [ ] [observable result tied to a plan criterion]
- [ ] `[verification command]` passes
- [ ] One focused commit contains only this todo's changes and is not pushed
### Verification
- Pending
### Result
- Pending
Use Blocked with an objective reason. Mark the top-level status Complete only when every required todo is complete with verified commit/result evidence (or an explicitly justified n/a).
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.
- 8d ago First seen · 60 lines · 36 tokens per session scan A dcc167a42ee1
write-todos is a skill published in the GitHub repository HazAT/pi-config (443 stars, last pushed 13d ago), licensed MIT. It adds 36 tokens to every session and 467 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.