todo

todo is a skill for Claude Code, Codex from postmelee/hyper-waterfall. It costs 71 tokens per session (1,250 once invoked), scanned A, original, MIT.

A workflow for writing and updating a daily task board in a dated Markdown file. It uses milestone tables to show what is planned, in progress, or complete.

In plain words
What is it for?
It helps create the daily board, update milestone statuses, record completion times, and maintain the backlog and operations sections when required.
Why use it?
It keeps the day’s work visible in one consistent place and records progress without turning the board into a longer project report.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/postmelee/hyper-waterfall/todo
Any agent
npx skills add postmelee/hyper-waterfall --skill todo
Clone the repo
git clone --depth 1 https://github.com/postmelee/hyper-waterfall

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 todo

README.md
[![agentmods](https://agentmods.dev/badge/skills/postmelee/hyper-waterfall/todo.svg)](https://agentmods.dev/skills/postmelee/hyper-waterfall/todo)
Your own site
<a href="https://agentmods.dev/skills/postmelee/hyper-waterfall/todo"><img src="https://agentmods.dev/badge/skills/postmelee/hyper-waterfall/todo.svg" alt="Measured on agentmods" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,250 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00071 $0.01250
Opus 5 $0.00036 $0.00625
Sonnet 5 $0.00014 $0.00250
Haiku 4.5 $0.00007 $0.00125

Measured 4d ago against content hash b5d1b8e7da32, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

templates/locales/en/mydocs/skills/todo/SKILL.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Daily Task Board Writing

Purpose

mydocs/orders/{yyyymmdd}.md is a one-page work board for the day. It is not a task plan, report, or technical note. It shows progress by milestone at a glance and records completion time.

Trigger

  • The task requester explicitly says "write today's tasks", "update orders", or "close today's tasks."
  • Apply this SKILL's format when task-start, task-stage-report, task-final-report, or pr-merge-cleanup updates the daily task board.
  • This SKILL is invoked directly.

Artifact

  • Target file: mydocs/orders/{yyyymmdd}.md
  • Writing language: use the selected Hyper-Waterfall locale for this repository.
  • Output format source: mydocs/_templates/orders.md

Standard Format

Use central template mydocs/_templates/orders.md first. The following is the minimal fallback format for cases where the template cannot be read.

  • Filename: yyyymmdd.md
  • Title: # Daily Tasks - YYYY-MM-DD
  • Body: at least one milestone section, plus a common operations section when needed
  • Each milestone section uses this table:
## M{milestone} - {milestone name}

| Issue | Task | Status | Notes |
|------|------|--------|-------|
| #{number} | {task} | Planned | {note} |
| #{number} | {task} | In progress | {note} |
| #{number} | {task} | Done | {note} |

Milestone Decision Rules

Before writing work, decide which milestone section it belongs to.

  1. Explicit task requester instruction
  2. If no explicit instruction exists, reuse the milestone structure already present in the same date's mydocs/orders/{yyyymmdd}.md
  3. If no same-date file exists, use an explicit milestone label from the target repository README.md roadmap or release notation
  4. If neither source decides it, do not invent a milestone name; ask the task requester

Cautions:

  • Distinguish roadmap transition notation from milestone names. For example, 0.5 -> 1.0 is a transition notation, not a section title.
  • Do not place work in a future milestone unless the task requester clearly specified it.
  • If README.md marks one milestone as current, use it as the default section for ambiguous work.

Read the full file on GitHub · 147 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. 4d ago First seen · 147 lines · 71 tokens per session scan A b5d1b8e7da32

Subscribe to this mod's changes

todo is a skill published in the GitHub repository postmelee/hyper-waterfall (78 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,250 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-30.

Related

Other skills, from other repositories

v1-milestone

Factory line for executing one milestone of the HAR v1.0.0 refactor (epic os-factory/har#225) — plan the wave of parallel subagents, implement each issue in its own HAR slot, ship stacked PRs, run the fixture-e2e milestone gate, and hand off for review. Use when asked to "run the next v1 milestone", "work on v1.0.0"…

os-factory/har · 110 tokens

git-issue

Prepare, review, create, or update evidence-based GitHub issues for the current repository with duplicate detection, repository-native templates, valid labels, and post-publication verification. Use when the user asks to draft, file, submit, publish, edit, or refine a GitHub issue, bug report, feature request…

diodeme/Gold-Band · 93 tokens

evaluator-write-qa

Internal Auto-Harness evaluator skill for sprint QA and QA report writing. Use only inside the Evaluator subagent during qa mode.

redker56/auto-harness · 32 tokens

evaluator-review-contract-parallel

Internal Auto-Harness evaluator skill for parallel sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.

redker56/auto-harness · 33 tokens

evaluator-write-qa-parallel

Internal Auto-Harness evaluator skill for parallel sprint QA and QA report writing. Use only inside the Evaluator subagent during evaluatorqaparallel.

redker56/auto-harness · 37 tokens

evaluator-write-retest-parallel

Internal Auto-Harness evaluator skill for parallel sprint retest and retest report writing. Use only inside the Evaluator subagent during evaluatorretestparallel.

redker56/auto-harness · 39 tokens