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/markmhendrickson/neotoma/analyzegit clone --depth 1 https://github.com/markmhendrickson/neotomaWrote 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/markmhendrickson/neotoma/analyze)<a href="https://agentmods.dev/commands/markmhendrickson/neotoma/analyze"><img src="https://agentmods.dev/badge/commands/markmhendrickson/neotoma/analyze.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.00000 | $0.00012 |
| Opus 5 | $0.00000 | $0.00006 |
| Sonnet 5 | $0.00000 | $0.00002 |
| Haiku 4.5 | $0.00000 | $0.00001 |
Grade A, and why
analyze 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.
What it actually says
../../foundation/agent_instructions/cursor_commands/analyze.md
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 · 1 lines · 0 tokens per session scan A 24b1d70b647d
analyze is a command published in the GitHub repository markmhendrickson/neotoma (31 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 12 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
tokenless-stats
Show Tokenless compression statistics.
remember
Save a durable fact or decision to gitmem memory.
memory-review
Review contested and stale gitmem memories and propose resolutions.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.
setup
Command "setup" from jazz-max/ruflo-hub, covering setting up ruv-swarm hooks, quick start, 1. initialize with hooks, 2. test hook functionality and test pre-edit hook.
agent-metrics
Command "agent-metrics" from jazz-max/ruflo-hub, covering agent-metrics, usage, options, examples and all agents metrics.