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 skills add monoes/monomind --skill monodocgit 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/skills/monoes/monomind/monodoc)<a href="https://agentmods.dev/skills/monoes/monomind/monodoc"><img src="https://agentmods.dev/badge/skills/monoes/monomind/monodoc/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/skills/monoes/monomind/monodoc"><img src="https://agentmods.dev/badge/skills/monoes/monomind/monodoc.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.00098 | $0.10557 |
| Opus 5.5 | $0.00039 | $0.04223 |
| Sonnet 5.5 | $0.00020 | $0.02111 |
| Haiku 4.5 | $0.00010 | $0.01056 |
Grade A, and why
monodoc 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 1,072 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monodoc — Technical Writing Workbench
Invoke via /monodoc or auto-routed from mastermind when the task is documentation.
Style profiles
Monodoc ships a Google profile (default) and supports overrides from other guides. Set via /monodoc --profile <name> or per-project in .monodoc.json.
| Profile | Base | Key differences from Google |
|---|---|---|
google (default) |
Google DDSG | Serial comma always; sentence case headings; "see" for cross-refs |
microsoft |
Microsoft Writing Style Guide | Contractions encouraged; deeper bias-free chapter; global-ready sentence caps |
stripe |
Stripe-inspired API docs | Prose-left/code-right layout; inline first-use definitions; error docs must state what/why/fix |
digitalocean |
DigitalOcean tutorial format | Rigid "Step N — Doing X" gerund headings for tutorials; prerequisite blocks mandatory |
minimal |
Subset of Google | Only errors, no warnings — for legacy codebases being incrementally improved |
Conflict resolution: when profiles disagree (serial comma, heading case, contraction policy), the active profile wins. The google profile is the tiebreaker for any rule not explicitly overridden.
Custom profile: create .monodoc.json at the project root:
{
"profile": "google",
"overrides": {
"serial_comma": true,
"heading_case": "sentence",
"contractions": "allowed",
"max_sentence_words": 26,
"readability_target": "grade-10",
"custom_word_list": {
"dont_use": {"leverage": "use", "utilize": "use"},
"preferred": {"repo": "repository"}
}
}
}
Commands
Core writing & review
| Command | Behavior |
|---|---|
/monodoc write <target> |
Write/rewrite a doc from scratch |
/monodoc review <file> |
Audit a doc against all rules; report violations with severity |
/monodoc fix <file> |
Review + auto-fix all violations in place |
/monodoc api <file> |
Generate/audit API reference comments (TSDoc/JSDoc) |
/monodoc readme |
Generate or rewrite the project README |
/monodoc guide <topic> |
Write a how-to guide for the given topic |
/monodoc tutorial <topic> |
Write a learning-oriented tutorial (distinct from how-to) |
| (no subcommand) | Infer mode from context — review if file exists, write if not |
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.
- 2d ago First seen · 1,072 lines · 98 tokens per session scan A f4df80abcb72
monodoc is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 98 tokens to every session and 10,557 once invoked, about $0.0004 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 skills, from other repositories
ppt-generation
Use this skill when the user requests to generate, create, or make presentations (PPT/PPTX). Creates visually rich slides by generating images for each slide and composing them into a PowerPoint file.
data-analysis
Use this skill when the user uploads Excel (.xlsx/.xls) or CSV files and wants to perform data analysis, generate statistics, create summaries, pivot tables, SQL queries, or any form of structured data exploration. Supports multi-sheet Excel workbooks, aggregation, filtering, joins, and exporting results to…
docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when…
docx
A guide for working with Microsoft Word documents in the .docx format. It covers reading, creating, editing, converting, exporting, and handling tracked changes.
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or…
xlsx
A guide for working with spreadsheet files such as Excel workbooks, CSV files, and TSV files.