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 agentmods add skills/postmelee/hyper-waterfall/todonpx skills add postmelee/hyper-waterfall --skill todogit clone --depth 1 https://github.com/postmelee/hyper-waterfallWrote 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/postmelee/hyper-waterfall/todo)<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>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 | $0.00071 | $0.01250 |
| Opus 5 | $0.00036 | $0.00625 |
| Sonnet 5 | $0.00014 | $0.00250 |
| Haiku 4.5 | $0.00007 | $0.00125 |
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.
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, orpr-merge-cleanupupdates 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.
- Explicit task requester instruction
- If no explicit instruction exists, reuse the milestone structure already present in the same date's
mydocs/orders/{yyyymmdd}.md - If no same-date file exists, use an explicit milestone label from the target repository
README.mdroadmap or release notation - 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.0is a transition notation, not a section title. - Do not place work in a future milestone unless the task requester clearly specified it.
- If
README.mdmarks one milestone as current, use it as the default section for ambiguous work.
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.
- 4d ago First seen · 147 lines · 71 tokens per session scan A b5d1b8e7da32
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.
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"…
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…
evaluator-write-qa
Internal Auto-Harness evaluator skill for sprint QA and QA report writing. Use only inside the Evaluator subagent during qa mode.
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.
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.
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.