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/danjdewhurst/todo-md-mcp/commitgit clone --depth 1 https://github.com/danjdewhurst/todo-md-mcpWhat 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.00013 | $0.00193 |
| Opus 5 | $0.00006 | $0.00097 |
| Sonnet 5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
commit 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 2d 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
I'll analyze the changed files and create a conventional commit message. Let me start by checking the git status and examining the changes.
!git status
Now let me examine the changes to understand what type of commit this should be:
!git diff --cached !git diff
Based on the changes, I'll analyze the type of modifications:
- New features (feat:)
- Bug fixes (fix:)
- Documentation changes (docs:)
- Code refactoring (refactor:)
- Performance improvements (perf:)
- Tests (test:)
- Build/tooling changes (build:, chore:, ci:)
- Code style changes (style:)
Let me add all changes and create an appropriate conventional commit:
!git add .
Now I'll create a conventional commit message based on the analysis of the changes and commit:
!git commit
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.
- 2d ago First seen · 31 lines · 13 tokens per session scan A b1ecbc4cfb08
commit is a command published in the GitHub repository danjdewhurst/todo-md-mcp (6 stars, last pushed 1y ago), licensed MIT. It adds 13 tokens to every session and 193 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-31.
Other commands, from other repositories
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
commit
Smart commit that stages only conversation-relevant changes.
commit-all
Group all changes semantically and commit each group separately.
commit
Based on the above changes, create a single git commit.
commit
This command helps you create well-formatted commits with conventional commit messages and emoji.
commit
Safe git commit practices for MindRoom.