Borrowing it
Nothing to install: this file belongs to edochi/mdvs. 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/edochi/mdvs/main/.claude/skills/todo/SKILL.mdgit clone --depth 1 https://github.com/edochi/mdvsWrote 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/edochi/mdvs/todo)<a href="https://agentmods.dev/skills/edochi/mdvs/todo"><img src="https://agentmods.dev/badge/skills/edochi/mdvs/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/edochi/mdvs/todo"><img src="https://agentmods.dev/badge/skills/edochi/mdvs/todo.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.00027 | $0.00778 |
| Opus 5.5 | $0.00011 | $0.00311 |
| Sonnet 5.5 | $0.00005 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TODO Tracking System
Spec TODOs live in docs/spec/todos/ as individual markdown files with YAML
frontmatter.
Finding TODOs
- Index:
docs/spec/todos/index.md— Single table sorted by ID with status, priority, and dates - Individual files:
docs/spec/todos/TODO-NNNN.md(zero-padded to 4 digits) - Quick lookup:
glob docs/spec/todos/TODO-*.md
Creating a New TODO
- Derive next ID: Find the highest existing ID and add 1 (do NOT fill gaps — IDs are never reused)
- Create file using this template:
---
id: <next_id>
title: <short title>
status: todo # todo | in-progress | done
priority: high # high | medium | low
created: <YYYY-MM-DD>
depends_on: [] # list of TODO IDs that must complete first
blocks: [] # list of TODO IDs this blocks
---
# TODO-NNNN: <Title>
## Summary
<1-3 sentences describing the goal>
## Details
<Full description: steps, design questions, files to create/update>
- Update
index.md: Add row to the table (sorted by ID)
Updating Status
Starting work (todo → in-progress)
- Update frontmatter:
status: in-progress - Update index.md if needed
Completing (in-progress → done)
- Update frontmatter:
status: done completed: <YYYY-MM-DD> files_created: [...] # files created during resolution files_updated: [...] # files modified during resolution - Replace
## Detailswith## Resolutioncontaining the resolution notes - Update index.md: change status, add completed date
Subsumption (absorbed by another TODO)
When a TODO is fully covered by another TODO's implementation:
- On the subsumed TODO:
status: done completed: <date of subsuming TODO's completion> subsumed_by: <subsuming TODO ID> - Rename
## Detailsto## Original Scope, add:## Resolution Subsumed by [TODO-NNNN](TODO-NNNN.md). <brief explanation>. - On the subsuming TODO, add:
subsumed: - <absorbed TODO ID>
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.
- 10d ago First seen · 109 lines · 27 tokens per session scan A 80e536780d9e
todo is a skill published in the GitHub repository edochi/mdvs (27 stars, last pushed 11d ago), licensed MIT. It adds 27 tokens to every session and 778 once invoked, about $0.0001 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-10-05.
Other skills, from other repositories
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.