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 commands/rand/mnemosyne/feature-checklistgit clone --depth 1 https://github.com/rand/mnemosyneWrote 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/commands/rand/mnemosyne/feature-checklist)<a href="https://agentmods.dev/commands/rand/mnemosyne/feature-checklist"><img src="https://agentmods.dev/badge/commands/rand/mnemosyne/feature-checklist.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.00011 | $0.03635 |
| Opus 5 | $0.00005 | $0.01818 |
| Sonnet 5 | $0.00002 | $0.00727 |
| Haiku 4.5 | $0.00001 | $0.00364 |
Grade A, and why
feature-checklist 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 3d 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 — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I will guide you through executing tasks for a feature implementation plan interactively, tracking progress in Beads and updating the plan as tasks are completed.
Usage:
/feature-checklist <feature-id>- Start interactive checklist for feature/feature-checklist <feature-id> --status- Show current progress only/feature-checklist <feature-id> --resume- Resume from last checkpoint
Instructions for me:
1. Load Feature Context
Load plan and tasks:
# Read implementation plan
cat .mnemosyne/artifacts/plans/<feature-id>-plan.md
# Get Beads tasks for feature (using hash IDs)
bd list --label feature:<feature-id> --json
Validate:
- If plan not found: "Error: Plan '' not found. Run /feature-plan first."
- If no Beads tasks: "Error: No tasks found for ''. Run /feature-tasks first."
- If both exist: Proceed to display
2. Display Interactive Checklist
Format:
Feature: <feature-name>
Plan: .mnemosyne/artifacts/plans/<feature-id>-plan.md
Tasks: <total> (<completed> complete, <in-progress> in progress, <open> ready)
Critical Path:
✅ bd-a1b2: Database Schema (4h) - COMPLETE
🔄 bd-c3d4: JWT Generation (6h) - IN PROGRESS
⏸️ bd-e5f6: Middleware Integration (4h) - BLOCKED by bd-c3d4
⬜ bd-g7h8: Testing (3h) - READY
Parallel Streams:
Stream A (Core Auth):
✅ bd-i9j0: Password Hashing (2h) - COMPLETE
🔄 bd-k1l2: Login Endpoint (3h) - IN PROGRESS
Stream B (Documentation):
⬜ bd-m3n4: API Documentation (2h) - READY
⬜ bd-o5p6: Integration Guide (1h) - BLOCKED by bd-m3n4
Progress: ████████░░░░░░░░ 40% (2/5 critical path)
Estimated Time Remaining: 12h (critical path), 6h (parallel)
Next Ready Tasks:
1. bd-c3d4 (IN PROGRESS): JWT Generation (6h)
2. bd-m3n4 (READY): API Documentation (2h)
What would you like to do?
[c] Continue current task (bd-c3d4)
[s] Start next ready task (bd-m3n4)
[v] View task details (enter task ID)
[p] Show full progress
[q] Quit checklist mode
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.
- 3d ago First seen · 475 lines · 11 tokens per session scan A ba71d579b6ab
feature-checklist is a command published in the GitHub repository rand/mnemosyne (84 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 3,635 once invoked, about $0.0001 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 commands, from other repositories
hatch3r-bug-plan
Diagnose a complex incident -- reproduce the symptom, rank root-cause hypotheses, design the fix path, and emit regression coverage items as a board-ready investigation.
hatch3r-debug
Standalone debug-and-fix workflow — add strategic debug logging, collect runtime logs from the user, perform root cause analysis, implement the fix, and clean up all debug artifacts.
hatch3r-feature-plan
Design a new capability -- draft user stories, acceptance criteria, data model, API surface, and sub-issue breakdown as an epic-shaped todo.md for greenfield features.
hatch3r-bug-pipeline
Run a known-cause bug fix through a 3-phase test-first pipeline -- reproduce + root-cause, regression-test + fix together, then root-cause-depth review -- with full sub-agent delegation.
hatch3r-incident-response
Drive a live production incident through a structured lifecycle -- triage + topology, bounded-autonomy mitigation, stakeholder communication, then a blameless post-mortem with runbook -- via delegated sub-agents.
hatch3r-handoff
Prepare, resume, list, complete, and prune cross-session handoff documents.