Borrowing it
Nothing to install: this file belongs to Bazilio-san/mcp-vkusvill. 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/Bazilio-san/mcp-vkusvill/master/.claude/skills/readme-generator/SKILL.mdgit clone --depth 1 https://github.com/Bazilio-san/mcp-vkusvillWrote 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/bazilio-san/mcp-vkusvill/readme-generator)<a href="https://agentmods.dev/skills/bazilio-san/mcp-vkusvill/readme-generator"><img src="https://agentmods.dev/badge/skills/bazilio-san/mcp-vkusvill/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/bazilio-san/mcp-vkusvill/readme-generator"><img src="https://agentmods.dev/badge/skills/bazilio-san/mcp-vkusvill/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.00092 | $0.03673 |
| Opus 5 | $0.00046 | $0.01836 |
| Sonnet 5 | $0.00018 | $0.00735 |
| Haiku 4.5 | $0.00009 | $0.00367 |
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 12d 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 — 273 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 tailored to MCP servers built on fa-mcp-sdk. The README answers three
progressive questions — what is this?, how do I use it?, how do I operate it? — without
drowning casual readers in operational detail.
Philosophy
Three-level information hierarchy:
Level 1 — What & how to use it (first 30 seconds for the consumer)
- What this MCP server is for
- What tools it exposes
- How to connect from Claude Code / Claude Desktop / Qwen Code (the simplest path)
Level 2 — Features & basics (interested reader)
- Enabled fa-mcp-sdk subsystems, project-specific capabilities, transports, essential config
Level 3 — Operations (deployer / maintainer)
- Build & run, full configuration, deep technical topics
Level 1 and 2 live in the main README. Level 3 content longer than ~15 lines moves to satellite
Markdown files under readme-docs/. The main README stays scannable; deep detail is one click away.
Scannability devices: Quick Links + collapsible blocks
Two devices keep the main README scannable even when it carries substantial inline content:
- Quick Links — a short navigation block right after the badges, pointing to the major sections a reader is likely to jump to. Include only headline topics (Tools, Quick Start, MCP Client Integration, Key Features, Configuration, Build & Run, Authentication, and any enabled feature sections that have their own heading — Impersonation, Admin Panel, Webhooks, Agent Tester, Skills, etc.). Do not dump a full TOC: secondary headings such as Overview, Transports, Stack, License stay out; minor sub-subsections stay out. Rule of thumb: 8–14 links, never more.
- Collapsible
<details>blocks — wrap content that must appear inline (so thedoc://readmeRAG pipeline picks it up as part of the main document) but whose volume would drown neighbouring sections on a casual scroll. The canonical case is the grouped Tools table (often 100+ rows across a dozen sub-tables). Use<details>when all three hold: (1) content belongs in this section, (2) it is long enough to push everything below off-screen, (3) a casual reader doesn't need every row right away. Do not use<details>for content readers need at a glance (Quick Start commands, Key Features bullets, the compact Configuration Basics table, Integration snippets). Seereference/templates.mdfor the required markup (the<br>after</summary>is mandatory — GitHub won't render the first child block correctly without it).
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.
- 12d ago First seen · 273 lines · 92 tokens per session scan A 60010c177c6d
readme-generator is a skill published in the GitHub repository Bazilio-san/mcp-vkusvill (1 stars, last pushed 2mo ago), licensed MIT. It adds 92 tokens to every session and 3,673 once invoked, about $0.0005 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…