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.
git clone --depth 1 https://github.com/HelloRuru/claude-memory-engineWrote 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/helloruru/claude-memory-engine/todo)<a href="https://agentmods.dev/commands/helloruru/claude-memory-engine/todo"><img src="https://agentmods.dev/badge/commands/helloruru/claude-memory-engine/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/commands/helloruru/claude-memory-engine/todo"><img src="https://agentmods.dev/badge/commands/helloruru/claude-memory-engine/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.00000 | $0.00214 |
| Opus 5.5 | $0.00000 | $0.00086 |
| Sonnet 5.5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
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 1mo 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.
What it actually says
/todo -- Cross-Project Task Tracker
Show pending tasks across all projects and suggest what to work on next.
Steps
- Read task file -- Load
memory/todo-status.md(or your configured task tracking file) - List all incomplete items -- Group by project, show status
- Suggest next step -- Prioritize by urgency
- Filter by project -- If the user specifies a project name, only show that project's tasks
Output Format
Pending Tasks
[Project A]
- [ ] Task description (added {date})
- [ ] Task description (added {date})
[Project B]
- [ ] Task description (added {date})
Suggested next: {most urgent task} because {reason}
Notes
- Keep the output scannable -- no walls of text
- If no tasks exist, say so and ask if the user wants to add some
- Tasks can be added, completed, or removed by editing the task file directly
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.
- 1mo ago First seen · 32 lines · 0 tokens per session scan A 374357953cf2
todo is a command published in the GitHub repository HelloRuru/claude-memory-engine (134 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 214 tokens. 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
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
handoff
Write a session handoff document for continuity.
update-docs
Scan recently modified files and update the matching documentation.
optimize
Run the credo optimisation audit for the current repo: a freshness check, then a read-only scan (conflict hotspots, changelog fragments, test-stage convention, dogma settings, parallelism readiness, and - only if the user says Yes when asked before the scan - instruction consistency across the global and repo…
gws-tasks
List, create, complete, and manage Google Tasks.