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 sergeyklay/.agents --skill manage-todogit clone --depth 1 https://github.com/sergeyklay/.agentsWrote 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/sergeyklay/.agents/manage-todo)<a href="https://agentmods.dev/skills/sergeyklay/.agents/manage-todo"><img src="https://agentmods.dev/badge/skills/sergeyklay/.agents/manage-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/sergeyklay/.agents/manage-todo"><img src="https://agentmods.dev/badge/skills/sergeyklay/.agents/manage-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.00132 | $0.01753 |
| Opus 5 | $0.00066 | $0.00877 |
| Sonnet 5 | $0.00026 | $0.00351 |
| Haiku 4.5 | $0.00013 | $0.00175 |
Grade A, and why
manage-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 11d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Management
Manage TODO.md - the sequenced project roadmap that drives all implementation work. TODO.md is the sequencing authority: milestones are deliberately ordered and each depends on the previous. Every mutation must preserve this invariant.
Authoritative format: See references/format-specification.md for the exact structural rules, naming conventions, line widths, indentation, and numbering scheme. Load this reference before any write operation.
Running scripts bundled with this skill
Script paths in this document (e.g. scripts/) are resolved relative to this SKILL.md file, not to your current working directory. If a relative command fails to resolve, prefix it with the path your platform loaded this SKILL.md from.
Fallback. If python3 cannot be located, analyze the script's purpose and logic and execute its intent with available tools, but warn the user that python is not available and the logic was executed with a fallback approach that may not be perfect.
Operations
Status - Progress Report
- Read
TODO.mdcompletely. - For each milestone, count completed (
[x]) vs total tasks. - Identify the active milestone - the first milestone with incomplete tasks.
- Report:
- Overall progress (completed / total tasks, percentage)
- Per-milestone breakdown (completed / total)
- Active milestone name and remaining tasks
- Any tasks that appear blocked (reference other incomplete tasks)
Next - Determine What to Work On
- Read
TODO.md. - Find the active milestone (first with incomplete tasks).
- Within that milestone, find the first
- [ ]task - this is the next task because milestones are sequential and tasks within them are ordered by dependency. - Return the task ID, description, and verify criteria.
- If the task references architecture sections, note them so the implementer knows what to read first.
Add - Insert a New Task
- Read
TODO.mdand references/format-specification.md. - Determine the correct milestone based on the task's theme and dependencies. Fundamental infrastructure goes earlier; feature-specific work goes later.
- Determine the next sequential task number within that milestone. If the last task is
N.M, the new task isN.(M+1). Never renumber existing tasks. - Write the task following the exact format:
- Checkbox:
- [ ] N.M - Description: imperative form, self-contained, wrapped at 90 characters
- Continuation lines: 6-space indent
- Verify: line describing how to confirm completion (tests, commands, or observable outcomes)
- Checkbox:
- Insert after the last task in the target milestone, before the next milestone heading.
- Validate the result (see Validate operation).
What ships with it
2 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.
- 11d ago First seen · 122 lines · 132 tokens per session scan A d4cca64a0a51
manage-todo is a skill published in the GitHub repository sergeyklay/.agents (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 132 tokens to every session and 1,753 once invoked, about $0.0007 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-31.
Other skills, from other repositories
glab-gitlab-issue
Read and manage GitLab issues through the glab CLI. Use when a user provides an issue ID and repository and asks to view issue details, comments, or uploaded images, publish comments, update assignees or labels, or manage issue time tracking (estimate/spent time) without using the web UI.
agentrq
Lead multiple agents to accomplish big tasks with specialized workspaces/agents by assigning tasks to specialized agents.
agentrq
Execute tasks assigned by humans or supervisor agents within a specific AgentRQ workspace. Use when you receive channel messages or need to report progress on tasks.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
plan
Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.
work
Execute Elixir/Phoenix plan tasks with progress tracking. Use after /phx:plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.