Borrowing it
Nothing to install: this file belongs to niclejeune/pi-agents-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/niclejeune/pi-agents-config/main/.pi/agent/skills/write-todos/SKILL.mdgit clone --depth 1 https://github.com/niclejeune/pi-agents-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/niclejeune/pi-agents-config/write-todos)<a href="https://agentmods.dev/skills/niclejeune/pi-agents-config/write-todos"><img src="https://agentmods.dev/badge/skills/niclejeune/pi-agents-config/write-todos/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/niclejeune/pi-agents-config/write-todos"><img src="https://agentmods.dev/badge/skills/niclejeune/pi-agents-config/write-todos.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.00074 | $0.01242 |
| Opus 5.5 | $0.00030 | $0.00497 |
| Sonnet 5.5 | $0.00015 | $0.00248 |
| Haiku 4.5 | $0.00007 | $0.00124 |
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 1mo 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Todos
Write todos that a worker agent can execute without access to the planning conversation. Every todo must be self-contained — a worker reading only the todo and the plan artifact must produce the correct result.
Why This Matters
Workers implement exactly what's described. If a todo contains a code sketch using plain classes, the worker builds plain classes — even if the plan says "use functional code for everything." Architectural intent that only lives in the plan's prose gets lost. Every constraint must be in the todo body itself.
Todo Structure
Every todo body follows this structure:
**Plan:** `plans/YYYY-MM-DD-<name>.md`
## What
[One paragraph: what this todo produces and why it matters]
## Constraints
- [Explicit architectural constraints that MUST be followed]
- [Libraries/patterns to use — or explicitly NOT use]
- [Reference existing code patterns: "Follow the pattern in src/foo.ts"]
## Files
- `src/path/to/file.ts` — [what this file does]
- `src/path/to/other.ts` — [what this file does]
## Expected Outcome
[Concrete description of what the finished code looks like]
### Example
[Short code snippet showing the expected shape — imports, key patterns, structure]
## Acceptance Criteria
- [ ] [Specific, verifiable criterion]
- [ ] [Another criterion]
- [ ] [Build/lint/test passes]
Rules
1. Constraints Are Explicit, Not Implied
If the plan says "use Effect v4 for all services," every service todo must repeat that:
| Bad (implicit) | Good (explicit) |
|---|---|
| "Build the EventBus service" | "Build the EventBus as an Effect v4 service. Import from effect. Use Effect.gen, Layer, and Context.Tag — not plain classes." |
| "Add WebSocket support" | "Add WebSocket support using the ws package. Do NOT use socket.io." |
| "Create the component" | "Create the component using React 19 + Tailwind v4 utility classes. No CSS modules, no styled-components." |
2. Examples Show The Real Shape
Include a short code snippet showing the expected import style, patterns, and structure. This is the single most effective way to prevent drift.
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.
- 1mo ago First seen · 136 lines · 74 tokens per session scan A 97ad8aae240f
write-todos is a skill published in the GitHub repository niclejeune/pi-agents-config (1 stars, last pushed 6mo ago), licensed MIT. It adds 74 tokens to every session and 1,242 once invoked, about $0.0003 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
trellis-workflow-enhancer
Audit and apply real, project-local Trellis integrations for Matt Pocock and Waza skills, with phase routing, hook injection, durable artifact handoffs, and smoke-test evidence. Use when a user wants to strengthen, compare, modernize, integrate, or debug Trellis with Matt/Waza workflows, especially when skills are…
orchestration
Coordinate parallel agent work. Use when decomposing complex tasks, running review/implementation in parallel, managing task lists, or choosing shared vs isolated workspaces.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
project-context-setup
Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions. Triggers on: "set up project context", "configure agent docs", "create CONTEXT.md", "setup agent workflow", "agent issue tracker setup", "triage…
generate-rfcs
Break the PRD into sequenced implementation RFCs under RFCs/ with an RFCS.md index, then cold-read each RFC for gaps.
implementation-task-spec
Use when you create an implementation board task directly - the required fields, one-role-one-deliverable rule, and dependency ordering.