Borrowing it
Nothing to install: this file belongs to OlliMakarova/mcp-metro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/OlliMakarova/mcp-metro/master/.claude/skills/readme-generator/SKILL.mdgit clone --depth 1 https://github.com/OlliMakarova/mcp-metroWrote 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/ollimakarova/mcp-metro/readme-generator)<a href="https://agentmods.dev/skills/ollimakarova/mcp-metro/readme-generator"><img src="https://agentmods.dev/badge/skills/ollimakarova/mcp-metro/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/skills/ollimakarova/mcp-metro/readme-generator"><img src="https://agentmods.dev/badge/skills/ollimakarova/mcp-metro/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.00121 | $0.04032 |
| Opus 5 | $0.00060 | $0.02016 |
| Sonnet 5 | $0.00024 | $0.00806 |
| Haiku 4.5 | $0.00012 | $0.00403 |
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 10d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server README Generator
Generates a README.md and its readme-docs/*.md satellites for an MCP server built on fa-mcp-sdk.
The main README is a showcase page: it hooks the reader with what the server can do and shows it
working; deep technical detail is one click away — in a satellite file, or in one of the two
collapsed reference sections at the end of the page.
Philosophy — showcase, not manual
Three reader roles, three destinations:
| Reader | Question | Where it's answered |
|---|---|---|
| Visitor (30 seconds) | What is this? Does it look alive? | Hook paragraph, screenshots, feature bullets |
| Evaluator (5 minutes) | Can I run it right now? | "Try it in 60 seconds", "Connect your client" |
| Integrator / operator | How exactly does X work? | The Documentation table → readme-docs/*.md |
Hard rule — no open reference material in the main README. No open parameter tables, no open
client-config JSON, no config-key tables, no endpoint lists, no auth priority orders, no Quick
Links block. Exactly two reference sections are allowed, both at the end of the page (after the
Documentation table) and both collapsed into <details> blocks:
- The tool, up close — parameters and answer contents, collapsed;
- Connect your client — one collapsed config block per MCP client.
Everything else that wants a reference table or a second code fence belongs in a satellite. Target: the collapsed view of the README stays around one–two screens (~100 visible lines); the raw file is longer because of the collapsed content, and that is fine.
Tone. Punchy but factual. Lead every feature bullet with the benefit, use concrete numbers (languages, route variants, endpoints), and never invent superlatives — "blazingly fast" and friends are banned. "Answers within a second of starting, thanks to the disk cache" is the register to hit: a strong claim, backed by a mechanism.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 282 lines · 121 tokens per session scan A 01ab3ef47737
readme-generator is a skill published in the GitHub repository OlliMakarova/mcp-metro (0 stars, last pushed 1mo ago), licensed MIT. It adds 121 tokens to every session and 4,032 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…