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/overview)<a href="https://agentmods.dev/commands/monoes/monomind/overview"><img src="https://agentmods.dev/badge/commands/monoes/monomind/overview/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/overview"><img src="https://agentmods.dev/badge/commands/monoes/monomind/overview.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.00023 | $0.00961 |
| Opus 5.5 | $0.00009 | $0.00384 |
| Sonnet 5.5 | $0.00005 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
hooks:overview 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hooks System Overview
Lifecycle hooks that connect Claude Code tool events to Monomind's outcome logging, agent routing, and session persistence. Hooks log edits, outcomes and trajectories to local JSON pattern files; no model is trained.
How It Works
Claude Code fires hook events (PreToolUse, PostToolUse, etc.) which trigger npx monomind hooks <subcommand> commands. The hooks system:
- Routes tasks to agents through the keyword picker (pick stats act as a bounded ranking prior)
- Records outcomes (edits, commands, tasks) in local JSON pattern files
- Persists session state across conversations
- Scans the repository (file types, import lines) into the memory store and local pattern log (
hooks pretrain)
CLI Subcommands
All hooks are invoked as npx monomind hooks <subcommand>:
Lifecycle Hooks
| Subcommand | Purpose |
|---|---|
pre-edit |
Context + agent suggestions before file edit |
post-edit |
Record edit outcome |
pre-command |
Risk assessment before running a command |
post-command |
Record command outcome |
pre-task |
Register task start, get agent suggestions + model routing |
post-task |
Record task completion |
session-end |
End session and persist state |
session-restore |
Restore a previous session |
Intelligence & Routing
| Subcommand | Purpose |
|---|---|
route |
Route task to optimal agent |
explain |
Explain routing decision |
pretrain |
Scan the repository (file types, import lines) into the memory store and local pattern log (no model is trained) |
metrics |
View recorded routing/outcome metrics |
model-route |
Route to optimal model (haiku/sonnet/opus) |
model-outcome |
Record model routing result |
model-stats |
View model routing statistics |
Coverage Tools
| Subcommand | Purpose |
|---|---|
coverage-route |
Route based on test coverage gaps |
coverage-suggest |
Suggest coverage improvements |
coverage-gaps |
List all coverage gaps with priorities |
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 · 111 lines · 23 tokens per session scan A ae0df356bf78
hooks:overview is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 961 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
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
github-modes
This document describes all GitHub integration modes available in Claude-Flow with ruv-swarm coordination. Each mode is optimized for specific GitHub workflows and includes batch tool integration for maximum efficiency.
pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.
prp-pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.