Borrowing it
Nothing to install: this file belongs to yusifeng/formax. 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/yusifeng/formax/main/.codex/skills/write-task-todo/SKILL.mdgit clone --depth 1 https://github.com/yusifeng/formaxWrote 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/yusifeng/formax/write-task-todo)<a href="https://agentmods.dev/skills/yusifeng/formax/write-task-todo"><img src="https://agentmods.dev/badge/skills/yusifeng/formax/write-task-todo/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/yusifeng/formax/write-task-todo"><img src="https://agentmods.dev/badge/skills/yusifeng/formax/write-task-todo.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.03389 |
| Opus 5.5 | $0.00022 | $0.01356 |
| Sonnet 5.5 | $0.00011 | $0.00678 |
| Haiku 4.5 | $0.00005 | $0.00339 |
Grade A, and why
write-task-todo 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 2mo 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Task Todo
Use this skill after analyze-task and after the analysis has been discussed and aligned when a task is large enough to need multiple implementation loops, commits, reviews, or cross-layer coordination.
This skill turns an analysis result into a single working task document:
docs/todolist.md
Purpose
Create a todo that is:
- structured
- execution-friendly
- test-aware
- biased toward definitions and interfaces before UI
This skill is not for coding and not for long-form design writing.
Preflight gate for large cross-layer tasks
Before writing docs/todolist.md, use a short Decision Draft when the task crosses any of these Formax boundaries:
- permissions / policy / approval / hooks
- runtime config / persistent settings / credentials / secrets
- tool runtime / prompt exposure / deferred exposure / ToolSearch
- SDK / REPL / app-server / Web / Electron entrypoints
- protocol boundaries, child processes, startup timing, session lifecycle, result mapping, files, binary payloads, or cleanup
Do not write the final todo until the Decision Draft is aligned. The draft should be short and must answer:
- Storage and config source: where data lives, who reads it, and who must not read it.
- Schema and strictness: accepted fields, rejected fields, default values, and unknown-field behavior.
- Startup / activation timing: which entrypoint may create side effects and which phases are pure.
- Permission model: whether existing Formax permission / approval / hook flow can express the behavior before adding new actions.
- Capability level: whether the feature is a tool, slash command, SDK control, hook, transcript renderer, config setting, or prompt exposure behavior.
- Entrypoints: REPL, SDK, app-server, Web, and Electron behavior.
- Result / IO boundaries: output caps, file locations, binary/media handling, cleanup, secrets, and timeout behavior.
- Non-goals: what is explicitly out of Phase 1 and what user-visible behavior that implies.
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.
- 2mo ago First seen · 322 lines · 54 tokens per session scan A c4a818d39e01
write-task-todo is a skill published in the GitHub repository yusifeng/formax (184 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 3,389 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-30.
write-task-todo compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| write-task-todoyusifeng/formax | Skill | 184 | 3mo ago | MIT | A | 54 | Codex |
| unbrokerKevRojo/Dulus | Skill | 508 | 3d ago | GPL-3.0 | A | 15 | Claude Code, Codex |
| obsidian-basesKevRojo/Dulus | Skill | 508 | 3d ago | GPL-3.0 | A | 63 | Claude Code, Codex |
| json-canvasKevRojo/Dulus | Skill | 508 | 3d ago | GPL-3.0 | A | 54 | Claude Code, Codex |
| obsidian-markdownKevRojo/Dulus | Skill | 508 | 3d ago | GPL-3.0 | A | 105 | Claude Code, Codex |
| obsidian-cliKevRojo/Dulus | Skill | 508 | 3d ago | GPL-3.0 | A | 102 | Claude Code, Codex |
| defuddleKevRojo/Dulus | Skill | 508 | 3d ago | GPL-3.0 | A | 74 | Claude Code, Codex |