agentmods.dev

polish-docs-meta

polish-docs-meta is a skill for Claude Code, Codex from cyanheads/git-mcp-server. It costs 53 tokens per session (2,257 once invoked), scanned A, original, Apache-2.0.

A release-preparation procedure for project documentation and metadata. It reviews the server’s exposed tools, resources, prompts, providers, authentication scopes, and related documentation after implementation is complete.

In plain words
What is it for?
Use it to finalize or clean up documentation, README content, and project metadata after adding or removing server capabilities. It can also be run again later because its steps check what still needs attention.
Why use it?
It helps catch documentation and metadata that no longer match the implemented project. It is intended for a release after checks and tests pass.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

not rated 240repo +1 13d ago A scan 53 tokens original Apache-2.0

Good fit Use it to finalize or clean up documentation, README content, and project metadata after adding or removing server capabilities. It can also be run again later because its steps check what still needs attention.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cyanheads/git-mcp-server/polish-docs-meta
View source ↗ cyanheads/git-mcp-server npmjs.com
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 cyanheads/git-mcp-server --skill polish-docs-meta
Clone the repo
git clone --depth 1 https://github.com/cyanheads/git-mcp-server

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.

agentmods badge for polish-docs-meta

README.md
[![agentmods](https://agentmods.dev/badge/skills/cyanheads/git-mcp-server/polish-docs-meta.svg)](https://agentmods.dev/skills/cyanheads/git-mcp-server/polish-docs-meta)
Your own site
<a href="https://agentmods.dev/skills/cyanheads/git-mcp-server/polish-docs-meta"><img src="https://agentmods.dev/badge/skills/cyanheads/git-mcp-server/polish-docs-meta.svg" alt="Measured on agentmods" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,257 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.02257
Opus 5 $0.00026 $0.01128
Sonnet 5 $0.00011 $0.00451
Haiku 4.5 $0.00005 $0.00226

Measured 7d ago against content hash f4f006dab618, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-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 7d 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 · 209 lines

How it starts

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

When to Use

  • Implementation is functionally complete (tools, resources, prompts, providers all working)
  • bun run devcheck passes, bun test passes
  • Preparing for a release, or making surface-area changes that affect README/metadata
  • 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

  • Tools/resources/prompts implemented and registered
  • bun run devcheck passes
  • bun test passes

If these aren't met, address them first.

Steps

1. Audit the Surface Area

Read the registered definitions. Build a mental model of what the server actually exposes — names, descriptions, input/output shapes, auth scopes. This inventory drives every document below.

Read:

  • src/mcp-server/tools/definitions/index.ts (the allToolDefinitions barrel)
  • Every src/mcp-server/tools/definitions/git-*.tool.ts
  • src/mcp-server/resources/definitions/index.ts
  • src/mcp-server/resources/definitions/git-working-directory.resource.ts
  • src/mcp-server/prompts/definitions/index.ts
  • src/mcp-server/prompts/definitions/git-wrapup.prompt.ts
  • src/config/index.ts (Zod config schema)
  • src/services/git/core/IGitProvider.ts (provider contract)

Capture: tool count (expected ~29), resource count, prompt count, git provider capabilities, required env vars.

2. README.md

Compare README content against the audit. Update tool/resource/prompt tables, env var lists, badges, and descriptions to match actual surface area. Don't rewrite sections that are already accurate.

Specific sync points:

  • Version badge reflects package.json version
  • Tool count in any feature-summary block matches actual count
  • The tools table lists every registered tool with a one-line description pulled from TOOL_DESCRIPTION
  • Config section lists every env var defined in src/config/index.ts with current defaults
  • Links to external deps ([Hono](https://hono.dev/), [MCP SDK](https://github.com/modelcontextprotocol/typescript-sdk), etc.) are on first mention
  • Transport examples (stdio + http) are current

Read the full file on GitHub · 209 lines

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.

  1. 7d ago First seen · 209 lines · 53 tokens per session scan A f4f006dab618

Subscribe to this mod's changes

polish-docs-meta is a skill published in the GitHub repository cyanheads/git-mcp-server (240 stars, last pushed 13d ago), licensed Apache-2.0. It adds 53 tokens to every session and 2,257 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-30.

Git and workflowReleasesWriting and docsaigit-servermcpmcp-servermodel-context-protocol
Related

Other skills, from other repositories

publish-release

Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.

Byggarepop/dotnet-mcp-orchestrator · 63 tokens

release-notes

Writes user-facing release notes from a git commit range. Use when asked to draft release notes, a changelog entry, or "what's new" text for a release.

Byggarepop/dotnet-mcp-orchestrator · 39 tokens

release-and-publish

Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…

cyanheads/pubmed-mcp-server · 112 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…

cyanheads/mcp-ts-core · 82 tokens

release-and-publish

Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…

cyanheads/mcp-ts-core · 112 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…

cyanheads/pubmed-mcp-server · 82 tokens