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/monoes/monomindWrote 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/monoes/monomind/setup)<a href="https://agentmods.dev/commands/monoes/monomind/setup"><img src="https://agentmods.dev/badge/commands/monoes/monomind/setup/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/monoes/monomind/setup"><img src="https://agentmods.dev/badge/commands/monoes/monomind/setup.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.00024 | $0.00698 |
| Opus 5.5 | $0.00010 | $0.00279 |
| Sonnet 5.5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
hooks:setup 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 yesterday.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setting Up Monomind Hooks
Quick Start
1. Initialize with Hooks
npx monomind init --hooks
This automatically creates .claude/settings.json with hook configurations.
2. Test Hook Functionality
# Test pre-edit hook
npx monomind hooks pre-edit --file src/utils.ts
# Test pre-task hook
npx monomind hooks pre-task -d "Implement user authentication"
# Test route
npx monomind hooks route -t "Fix authentication bug"
3. Customize Hooks
Edit .claude/settings.json to configure which hooks fire on which Claude Code events:
{
"hooks": {
"PreToolUse": [
{
"matcher": "^(Write|Edit|MultiEdit)$",
"hooks": [{
"type": "command",
"command": "npx monomind hooks pre-edit --file '${tool.params.file_path}'"
}]
},
{
"matcher": "^Bash$",
"hooks": [{
"type": "command",
"command": "npx monomind hooks pre-command --command '${tool.params.command}'"
}]
}
],
"PostToolUse": [
{
"matcher": "^(Write|Edit|MultiEdit)$",
"hooks": [{
"type": "command",
"command": "npx monomind hooks post-edit --file '${tool.params.file_path}' --success true"
}]
},
{
"matcher": "^Bash$",
"hooks": [{
"type": "command",
"command": "npx monomind hooks post-command --command '${tool.params.command}' --success true"
}]
}
]
}
}
Common Patterns
Task Tracking (manual)
# Record task start
npx monomind hooks pre-task -d "Implement auth module"
# After completing work, record result
npx monomind hooks post-task -i task-123 --success true
Route Before Spawning
# Get agent recommendation for a task
npx monomind hooks route -t "Optimize database queries"
# Understand why an agent was chosen
npx monomind hooks explain -t "Fix authentication bug"
Bootstrap from Repository
# Pretrain on current repo (medium depth + embeddings)
npx monomind hooks pretrain
# Deep analysis only, no embeddings
npx monomind hooks pretrain --depth deep --no-with-embeddings
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.
- yesterday First seen · 131 lines · 24 tokens per session scan A 0f13b1132285
hooks:setup is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 698 once invoked, about $0.0001 per session on Opus 5.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-10-26.
Other commands, from other repositories
doctor
Health-check the harness: kernel load, MCP wiring, memory backend, host adapter.
review-diff
Review the current working diff for correctness, security, and reuse.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
prp-plan
Create comprehensive feature implementation plan with codebase analysis and pattern extraction.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
checklist
Generate a custom checklist for the current feature based on user requirements.