What is polish-docs-meta?

A checklist for making an MCP server ready to publish. An MCP server is a service that exposes tools, data, or prompts for AI applications.

It is for auditing registered tools and resources, finalizing documentation and project metadata, and preparing a server for release.

It checks the server's public surface and documentation after implementation, tests, and development checks are complete.

polish-docs-meta — Skill for Claude Code by wallieinformal201

Install

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.

Any agent

npx skills add wallieinformal201/pentest-mcp-server --skill polish-docs-meta

Clone the repo

git clone --depth 1 https://github.com/wallieinformal201/pentest-mcp-server

Made for: Claude Code.

Or install @cyanheads/pentest-mcp-server, the plugin that ships this one along with the rest of its 31 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/wallieinformal201/pentest-mcp-server/polish-docs-meta/github.svg)](https://agentmods.dev/skills/wallieinformal201/pentest-mcp-server/polish-docs-meta)

Your own site

<a href="https://agentmods.dev/skills/wallieinformal201/pentest-mcp-server/polish-docs-meta"><img src="https://agentmods.dev/badge/skills/wallieinformal201/pentest-mcp-server/polish-docs-meta/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/wallieinformal201/pentest-mcp-server/polish-docs-meta"><img src="https://agentmods.dev/badge/skills/wallieinformal201/pentest-mcp-server/polish-docs-meta.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,712 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00054	$0.03712
Opus 5	$0.00027	$0.01856
Sonnet 5	$0.00011	$0.00742
Haiku 4.5	$0.00005	$0.00371

Measured 10d ago against content hash e82f8f98641d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

polish-docs-meta 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.

skills/polish-docs-meta/SKILL.md · 272 lines

How it starts

The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When to Use

Server implementation is functionally complete (tools, resources, prompts, services all working)
bun run devcheck passes, tests pass
You're preparing for first commit, first release, or making the repo public
User says "polish", "polish docs", "finalize", "make it ship-ready", "clean up docs", or similar
Re-running after adding/removing tools, resources, or other surface area changes

Prefer running after implementation is complete, but safe to re-run at any point — steps are idempotent.

Companion: pair with security-pass for a full pre-ship review — this skill polishes docs and metadata; security-pass audits handlers for MCP-specific security gaps.

Prerequisites

All tools/resources/prompts implemented and registered
bun run devcheck passes
Tests pass (bun run test)

If these aren't met, address them first.

Steps

1. Audit the Surface Area

Read all tool, resource, and prompt definitions. Build a mental model of what the server actually does — names, descriptions, input/output shapes, auth scopes. This inventory drives every document below.

Read:

src/index.ts (what's registered in createApp())
All files in src/mcp-server/tools/definitions/
All files in src/mcp-server/resources/definitions/
All files in src/mcp-server/prompts/definitions/
All files in src/services/ (if any)
src/config/server-config.ts (if any)

Capture: tool count, resource count, prompt count, service count, required env vars.

2. README.md

Read references/readme.md for structure and conventions. If README.md doesn't exist, create it from scratch. If it exists, diff the current content against the audit — update tool/resource/prompt tables, env var lists, and descriptions to match the actual surface area. Don't rewrite sections that are already accurate.

The bold header tagline (the <b> text inside the first <p>) must match the package.json description. The surface count is a nested <div> inside the same <p>, separated by •.

Read the full file on GitHub · 272 lines

Files

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.

Changes

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 · 272 lines · 54 tokens per session scan A e82f8f98641d

Subscribe to this mod's changes

polish-docs-meta is a skill published in the GitHub repository wallieinformal201/pentest-mcp-server (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 54 tokens to every session and 3,712 once invoked, about $0.0003 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.

0x4m4 Writing and docs agentic-ai ai-penetration-testing appsecco asyncio kali

orchestrate

Delegate a LARGE, multi-part goal to Volante's cross-model orchestration engine via the volanterun MCP tool. Use ONLY when the request genuinely decomposes into several sub-tasks that benefit from routing across different models (e.g. "research X, draft Y, then produce Z"). Do NOT use it for simple, single-step, or…

ribato22/volante · 80 tokens

worker-integration

Worker-Agent integration for intelligent task dispatch and performance tracking.

ruvnet/ruflo · 14 tokens

foundry-config-setup

Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.

microsoft/agent-framework · 65 tokens

polish-docs-meta