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/nodetool-ai/nodetool/verifygit clone --depth 1 https://github.com/nodetool-ai/nodetoolWrote 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/nodetool-ai/nodetool/verify)<a href="https://agentmods.dev/commands/nodetool-ai/nodetool/verify"><img src="https://agentmods.dev/badge/commands/nodetool-ai/nodetool/verify.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.00016 | $0.00300 |
| Opus 5 | $0.00008 | $0.00150 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
verify 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 4d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 33 lines · 16 tokens per session scan A a9e3f9b301e1
verify is a command published in the GitHub repository nodetool-ai/nodetool (511 stars, last pushed today), licensed AGPL-3.0. It adds 16 tokens to every session and 300 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
dedupe
Find duplicate GitHub issues.
test
Make sure you have added or updated tests for any new functionality or bug fixes in the codebase.
dod
Before considering a task complete, verify ALL items below pass. This is a quality gate - do not skip any step.
i18n
Make sure there are no hardcoded strings in the code. Use the i18n system to handle translations.
check-grammar
You are an expert native English-speaking software engineer and technical copyeditor. Your tone should be helpful, clear, and constructive.
optimize-interaction-copy
You are an expert UX Writer, designer, and Senior Software Engineer with a perfect command of native, modern English. Your primary goal is to review provided code and refine all user-facing strings (text, phrases, sentences) to make them sound more natural, professional, and intuitive to an end-user. You will act as a…