pi-agents-config: Skill for Claude Code

.pi/agent/skills/write-todos/SKILL.md

write-todos is a skill for Claude Code, Codex from niclejeune/pi-agents-config. It costs 74 tokens per session (1,242 once invoked), scanned A, original, MIT.

A task-writing skill that turns a plan into self-contained todos for coding workers.

In plain words
What is it for?
Use it to split planned work into actionable tasks that state the expected result, constraints, files, examples, and completion conditions.
Why use it?
It prevents important architectural decisions and constraints from being lost when work is handed from a planner to an implementer.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is niclejeune/pi-agents-config's own configuration. It tells Claude Code and Codex how to work on pi-agents-config itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pi-agents-config configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/niclejeune/pi-agents-config/main/.pi/agent/skills/write-todos/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/niclejeune/pi-agents-config

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for write-todos

README.md
[![agentmods](https://agentmods.dev/badge/skills/niclejeune/pi-agents-config/write-todos/github.svg)](https://agentmods.dev/skills/niclejeune/pi-agents-config/write-todos)
Your own site
<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.

agentmods 80×15 button for write-todos

Your own site · 80×15
<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>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,242 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.01242
Opus 5 $0.00037 $0.00621
Sonnet 5 $0.00015 $0.00248
Haiku 4.5 $0.00007 $0.00124

Measured 10d ago against content hash 97ad8aae240f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 10d 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.

.pi/agent/skills/write-todos/SKILL.md · 136 lines

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.

Read the full file on GitHub · 136 lines

Changes

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.

  1. 10d ago First seen · 136 lines · 74 tokens per session scan A 97ad8aae240f

Subscribe to this mod's changes

write-todos is a skill published in the GitHub repository niclejeune/pi-agents-config (1 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 1,242 once invoked, about $0.0004 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-31.

Related

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…

lei1024/trellis-workflow-enhancer · 79 tokens

orchestration

Coordinate parallel agent work. Use when decomposing complex tasks, running review/implementation in parallel, managing task lists, or choosing shared vs isolated workspaces.

spences10/skills · 35 tokens

flowai-live-dashboard-template

Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log), KPI stat row, member table, role distribution bar chart, online presence and activity sparklines, and a top-contributors panel, all in a single self-contained HTML file with light/dark theming, hoverable…

nexu-io/open-design · 114 tokens

team-okrs

OKR tracker page — quarter banner, three objectives with their key results as progress bars, owner avatars, status pills, and a "this quarter at a glance" sidebar. Use when the brief mentions "OKRs", "key results", "objectives", or "目标".

nexu-io/open-design · 62 tokens

huashu-keynote-black

OpenDesign's all-hands: the year in review, the three priorities, and what every team owns next quarter. Built as a decision-grade corporate strategy deck for whole company.

nexu-io/open-design · 43 tokens

html-ppt-knowledge-arch-blueprint

OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.

nexu-io/open-design · 52 tokens