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-wiki)<a href="https://agentmods.dev/commands/monoes/monomind/monograph-wiki"><img src="https://agentmods.dev/badge/commands/monoes/monomind/monograph-wiki/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-wiki"><img src="https://agentmods.dev/badge/commands/monoes/monomind/monograph-wiki.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.00031 | $0.00648 |
| Opus 5.5 | $0.00012 | $0.00259 |
| Sonnet 5.5 | $0.00006 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
monograph:monograph-wiki 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
monograph wiki
Scan all docs and PDFs in the project and build a searchable knowledge graph. Optimized for documentation-heavy projects.
Usage
npx monomind monograph wiki [options]
Options
| Flag | Short | Type | Default | Description |
|---|---|---|---|---|
--path |
-p |
string | cwd | Root path to scan |
--llm |
— | boolean | false |
Enrich with Claude semantic extraction (requires ANTHROPIC_API_KEY) |
--llm-sections |
— | number | 100 |
Max sections for LLM enrichment |
--force |
-f |
boolean | false |
Force full rebuild |
Examples
# Build knowledge graph from all docs and PDFs
npx monomind monograph wiki
# With Claude semantic extraction
npx monomind monograph wiki --llm
# Deep enrichment — process 200 sections with Claude
npx monomind monograph wiki --llm --llm-sections 200
# Specific docs folder
npx monomind monograph wiki -p ./docs
# Force full rebuild
npx monomind monograph wiki --force
What Gets Indexed
Scans for files with extensions: .md, .mdx, .txt, .rst, .pdf
| Type | Processing |
|---|---|
.md / .mdx |
Headings → Section nodes with hierarchical structure |
.txt / .rst |
Chunked → Section nodes |
.pdf |
Text extracted → PDF chunk nodes |
Difference from build
build |
wiki |
|
|---|---|---|
| Code files | Yes | No |
| Documents | Yes | Yes |
| PDFs | Yes | Yes |
| LLM default sections | 50 | 100 |
| Best for | Mixed projects | Doc-heavy / knowledge bases |
LLM Enrichment
With --llm, Claude extracts semantic relationships between sections:
DESCRIBES— section explains a conceptCAUSES— one event leads to anotherPART_OF— hierarchical membershipCO_OCCURS— concepts appear together
These INFERRED edges make semantic search significantly more accurate.
After Build
# Search your wiki
npx monomind monograph search -q "your query"
# View statistics
npx monomind monograph stats
# Auto-rebuild on edits
npx monomind monograph watch
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 · 92 lines · 31 tokens per session scan A 5d041a1a2fd4
monograph:monograph-wiki is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 648 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
slm-media
Save pictures and PDFs in SuperLocalMemory and find them again by describing them. Covers when to save a picture or document, remembermedia, rememberdocument, getmedia, mediastatus and mediauploadlink, how recall returns pictures and PDF pages, the limits, what stays private, turning the feature on with slm media (16…
mem-doc
Ingest a local document (PDF, Markdown, text, image, docx…) into the memory vault as a single-shot archive.
slides
A presentation-making command that creates slides from a topic using Manus Slides, with 24 stated visual styles. It can export the result as PPTX, PDF, or HTML files.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.