What is polish-docs-meta?

A finishing checklist for an MCP server, a program that lets AI systems use tools and data sources. It reviews the server’s documented tools, resources, prompts, services, tests, and project metadata before release.

Preparing a completed MCP server for shipping, updating documentation after interface changes, and checking project metadata. It is intended for use after implementation, tests, and the development check pass.

It helps find mismatches between what the server actually provides and what its documentation says. It also organizes final cleanup for a first commit, release, or public repository.

polish-docs-meta — Skill for Claude Code and Codex by magnusquest

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 magnusquest/startgg-mcp --skill polish-docs-meta

Clone the repo

git clone --depth 1 https://github.com/magnusquest/startgg-mcp

Made for: Claude Code, Codex.

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/magnusquest/startgg-mcp/polish-docs-meta/github.svg)](https://agentmods.dev/skills/magnusquest/startgg-mcp/polish-docs-meta)

Your own site

<a href="https://agentmods.dev/skills/magnusquest/startgg-mcp/polish-docs-meta"><img src="https://agentmods.dev/badge/skills/magnusquest/startgg-mcp/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/magnusquest/startgg-mcp/polish-docs-meta"><img src="https://agentmods.dev/badge/skills/magnusquest/startgg-mcp/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 1,249 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.01249
Opus 5.5	$0.00022	$0.00500
Sonnet 5.5	$0.00011	$0.00250
Haiku 4.5	$0.00005	$0.00125

Measured 2mo ago against content hash 6034edc3a03e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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 · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 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.

Prerequisites

All tools/resources/prompts implemented and registered
bun run devcheck passes
Tests pass (npm 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.

3. Agent Protocol (CLAUDE.md / AGENTS.md)

Update the project's agent protocol file to reflect the actual server.

Read references/agent-protocol.md for the full update checklist, then review the current file and address what's stale or missing:

If a "First Session" onboarding block is still present, remove it
If example patterns still use generic/template names (e.g., searchItems, itemData), replace with real definitions from this server
If server-specific skills were added, update the skills table
Verify the structure diagram matches the actual directory layout
If custom scripts were added to package.json, update the commands table

Read the full file on GitHub · 139 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.

2mo ago First seen · 139 lines · 54 tokens per session scan A 6034edc3a03e

Subscribe to this mod's changes

polish-docs-meta is a skill published in the GitHub repository magnusquest/startgg-mcp (1 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 1,249 once invoked, about $0.0002 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-08-31.

Building agents Writing and docs

polish-docs-meta next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
polish-docs-metamagnusquest/startgg-mcp	Skill	1	6mo ago	Apache-2.0	A	54	Claude Code, Codex
imagegenopenai/codex	Skill	135k	today	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	100k	today	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	5d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	316k	8d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code