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 gabrieldabbah/genesis --skill todogit clone --depth 1 https://github.com/gabrieldabbah/genesisWrote 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/gabrieldabbah/genesis/todo)<a href="https://agentmods.dev/skills/gabrieldabbah/genesis/todo"><img src="https://agentmods.dev/badge/skills/gabrieldabbah/genesis/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.1 | $0.00156 | $0.00956 |
| Opus 5 | $0.00078 | $0.00478 |
| Sonnet 5 | $0.00031 | $0.00191 |
| Haiku 4.5 | $0.00016 | $0.00096 |
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 7d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain the master TODO
Keep the project's docs/TODO.md (the live backlog) and docs/TODO-done.md
(the dated archive) accurate, honest, and well-ordered. Template + full legend live in those files' headers.
Status markers (status first, then optional priority)
[ ]not started ·[~]in progress / partial ·[?]implemented but unverified (code looks done, not yet proven) ·[x]done and verified.[P]is a separate priority marker, prepended:[ ] [P] ….- Verification type on every item:
🤖= an agent can prove it with a test/command ·🙋= needs a human (manual test, judgment, real-world check). Every item carries a→ verify:line stating exactly how. - Exposure tags (optional):
🌍public-eligible ·🔒internal-only ·⚖needs ToS/Privacy review.
What this skill does
- Add an item to the right section with a status marker, verification type +
→ verify:,deps:, and any tags. New work without a clear verify is incomplete — ask or infer one. - Advance status:
[ ]→[~]→[?]→[x]. Set[?]when code is written but the verify has not passed yet; do not jump to[x]on assumption. - Sort open items by priority → ease → dependency count (quick unblocked wins first, then foundational,
then dependent systems). Keep
## 0. In-flightto what's actively in progress. - Move on done — a whole section, not an item. When a heading section holds no open items at all, move the
section into
docs/TODO-done.mdunder today's real date (read it from the system, never invent it), preserving the descriptions and the evidence (the command that passed, the PR, who verified). An[x]inside a section still in progress stays: it records that one part is built while the unit is not, and moving a finished part out of an unfinished whole strips the whole of the context needed to finish it. - After a move, grep the moved titles — index lines elsewhere that pointed into that section now dangle.
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.
- 7d ago First seen · 49 lines · 156 tokens per session scan A 5ecd672407ee
todo is a skill published in the GitHub repository gabrieldabbah/genesis (4 stars, last pushed 1mo ago), licensed MIT. It adds 156 tokens to every session and 956 once invoked, about $0.0008 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
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
workspace
Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
unharness
Safely leave Citadel using the active adoption receipt. Produces a no-write, reviewable plan, preserves a portable archive, removes only exact owned material, and reports modified or externally registered surfaces as retained or unknown. Legacy installs must be imported before exact leave is claimed.
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
github-backlog-triage
Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.