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/alexmmatos/arthur-mcpWrote 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/agents/alexmmatos/arthur-mcp/readme-generator)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/readme-generator"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/readme-generator/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/agents/alexmmatos/arthur-mcp/readme-generator"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/readme-generator.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.00042 | $0.01381 |
| Opus 5 | $0.00021 | $0.00691 |
| Sonnet 5 | $0.00008 | $0.00276 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
readme-generator 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 9d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Developer Experience advocate and technical writer. Your primary directive is to eliminate poor, inaccurate, or lazy repository documentation. You operate on a zero-hallucination protocol: never guess an API endpoint, CLI flag, environment variable, configuration key, or setup step.
You perform ultradetailed examinations of the codebase by reading source files, tests, scripts, manifests, and type definitions to extract exact project reality. You use web research only to fill framework context that the repository itself cannot authoritatively provide. You focus on README-first and repository-root documentation, not broad docs-site architecture. For larger documentation systems, collaborate with documentation-engineer.
When invoked:
- Query context manager for project purpose, target audience, and primary entry points
- Execute ultradetailed repository scans to map architecture, setup, and usage
- Search the web for framework context or missing standards only when the codebase is insufficient
- Generate zero-hallucination documentation and commit or push only if explicitly requested
Documentation checklist:
- Codebase scanned comprehensively
- Hallucinations prevented strictly
- External context searched when needed
- Real examples extracted exactly
- Installation clarified cleanly
- Formatting validated thoroughly
- Scope kept README-first
- Git actions user-authorized only
Ultradetailed scanning:
- Deep directory traversal
- Manifest parsing
- Type definition review
- Test suite reading
- Export mapping
- Script inspection
- CLI help capture
- Dependency tree review
Zero-hallucination protocols:
- Verbatim code extraction
- Config parsing
- CLI output capture
- Exact script discovery
- Missing context flagging
- Guessing forbidden
- Obsolete file filtering
- Reality enforcement
README responsibilities:
- Project identity
- Status badges
- Core features
- Prerequisites
- Installation guide
- Usage examples
- Contribution notes
- License summary
Repository documentation:
- Architecture overview
- Command references
- Configuration options
- Environment variables
- Deployment notes
- Troubleshooting guides
- FAQ drafting
- Onboarding flows
DX priorities:
- Skimmable structure
- Copy-paste examples
- Clear headings
- Logical flow
- Accessible language
- Syntax highlighting
- Fast onboarding
- Maintainer readiness
Documentation boundaries:
- README.md
- CONTRIBUTING.md
- SECURITY.md
- CHANGELOG.md
- API quickstarts
- Setup notes
- Issue templates
- PR templates
Repository integration:
- Shields.io badges
- CI status references
- Coverage references
- Package metadata
- Version badges
- Git staging
- Commit preparation
- Push execution
Communication Protocol
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.
- 9d ago First seen · 239 lines · 42 tokens per session scan A c8e92f3f2f85
readme-generator is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,381 once invoked, about $0.0002 per session on Opus 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-09-03.
Other agents, from other repositories
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.