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 skills add jdrhyne/agent-skills --skill todo-trackergit clone --depth 1 https://github.com/jdrhyne/agent-skillsWrote 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/jdrhyne/agent-skills/todo-tracker)<a href="https://agentmods.dev/skills/jdrhyne/agent-skills/todo-tracker"><img src="https://agentmods.dev/badge/skills/jdrhyne/agent-skills/todo-tracker/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/jdrhyne/agent-skills/todo-tracker"><img src="https://agentmods.dev/badge/skills/jdrhyne/agent-skills/todo-tracker.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.00055 | $0.01271 |
| Opus 5 | $0.00028 | $0.00635 |
| Sonnet 5 | $0.00011 | $0.00254 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
todo-tracker 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TODO Tracker
Maintain a portable Markdown task file without a service or database. Use the bundled script for every operation; do not edit task lines with ad hoc regex commands.
Runtime requirements: Bash and standard awk, cp, chmod, mkdir, mktemp, and mv utilities. Tasks are stored in a user-configurable local Markdown file.
File and Script
TODO_FILEselects the task file. Default:TODO.mdin the current workspace.- Always invoke the bundled script through
{baseDir}so execution does not depend on the current directory. - Read operations do not create a file.
- Writes use an adjacent lock, atomic same-directory renames, mode
600, and a recoverable previous-state backup at${TODO_FILE}.bak. ${TODO_FILE}.next-idis an adjacent mode-600monotonic ID counter. Keep it with the task file when moving or restoring the tracker; backup rotation must not replace or delete it.
TODO_FILE="$PWD/TODO.md" bash "{baseDir}/scripts/todo.sh" list
Do not use a machine-specific path. Quote TODO_FILE, IDs, and item text.
Stable Identity
New tasks receive monotonic IDs such as T000001. Task text is matched literally and exactly, never as a regex or substring.
- Under the same writer lock, the script bootstraps the counter from the current task file,
${TODO_FILE}.bak, and any valid existing counter. It reserves and atomically persists the next counter value before publishing a task-file mutation, so a crash may create an ID gap but cannot reuse an ID. - Only the structured ID field immediately after a task checkbox participates in counter bootstrapping. ID-looking text inside a task title remains literal task content and never advances the counter.
- A missing counter is created safely on the next write. A corrupt, symbolic-link, non-regular, or non-
0600counter fails closed; do not delete or reset it to bypass the check. - Prefer an ID for
doneand always use an ID for approved removal. - An exact-text target must match one task only.
- Duplicate open task text is rejected.
- An ambiguous exact-text target is rejected and the script reports the matching IDs.
- On the first operation that must resolve or mutate a legacy file, task lines without IDs are assigned deterministic IDs under the writer lock and the migration is persisted atomically; the original remains in the backup. A removal preview can trigger this recoverable metadata migration even though it removes no task.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 118 lines · 55 tokens per session scan A 8270d796cfcb
todo-tracker is a skill published in the GitHub repository jdrhyne/agent-skills (241 stars, last pushed 10d ago), licensed MIT. It adds 55 tokens to every session and 1,271 once invoked, about $0.0003 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
prd
A guide for writing a PRD, or Product Requirements Document, which explains what a product or feature should achieve and who it is for. It covers goals, users, success measures, limits, prior work, and excluded scope.
product-discovery
Product discovery workflow with OST, assumption testing, and interview scripts.
team-coordination
Inspired by the Disp8chTeam multi-agent coordination framework — enables you to organize AI agents into collaborative crews with workspace isolation, P2P messaging, and dependency-aware task management.
planner
Interactive planning and execution for complex tasks. Use when breaking down multi-step projects (planning) or executing approved plans through delegation (execution). Planning creates milestones with specifications; execution delegates to specialized agents. Use when you say "plan this feature", "create…
execution-plans
Manage execution plans as versioned artifacts with progress tracking and decision logs. Use when you say "create execution plan", "update plan progress", "log decision", "complete plan", or "abandon plan". Do NOT use to break work into milestones or delegate tasks (use planner).
openakita/skills@github-automation
Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.