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/monograph-stats)<a href="https://agentmods.dev/commands/monoes/monomind/monograph-stats"><img src="https://agentmods.dev/badge/commands/monoes/monomind/monograph-stats/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/monograph-stats"><img src="https://agentmods.dev/badge/commands/monoes/monomind/monograph-stats.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.00028 | $0.00382 |
| Opus 5.5 | $0.00011 | $0.00153 |
| Sonnet 5.5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
monograph:monograph-stats 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.
What it actually says
monograph stats
Show knowledge graph statistics — node counts by type, edge type breakdown, and top concepts by importance.
Usage
npx monomind monograph stats [options]
Options
| Flag | Short | Type | Default | Description |
|---|---|---|---|---|
--path |
-p |
string | cwd | Root path (location of .monomind/monograph.db) |
--top |
— | number | 10 |
Number of top concepts to show |
Examples
# Show graph statistics
npx monomind monograph stats
# Show top 20 concepts
npx monomind monograph stats --top 20
# Stats for a different project path
npx monomind monograph stats -p ./other-project
Output
- Nodes table — count per node type (
File,Section,Function,Class,Concept) with bar chart - Edges table — count per relation type (
IMPORTS,TAGGED_AS,CO_OCCURS,INFERRED, etc.) - Top N Concepts — ranked by importance score and section count, shown with star ratings
- Summary line — CO_OCCURS edge count and LLM-inferred edge count
MCP Tool
mcp__monomind__monograph_stats()
See Also
monograph build— build or rebuild the graphmonograph search— search across nodesmonograph watch— auto-rebuild on changes
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 · 54 lines · 28 tokens per session scan A f099bea1c87e
monograph:monograph-stats is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 382 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
claude-flow-memory
Interact with Claude-Flow memory system.
sessions
Manage OpenAI Codex session history, aliases, and session metadata.
checkpoint
Create an identified recovery point and inspect exact restoration differences.
recall
Retrieve scoped lessons and evaluate their assumptions, conflicts, and applicability.
save-session
Save current session state to a dated file in /.codex/session-data/ so work can be resumed in a future session with full context.
checklist
Generate a custom checklist for the current feature based on user requirements.