polish-docs-meta

polish-docs-meta is a skill for Claude Code from cyanheads/finnhub-mcp-server. It costs 54 tokens per session (4,125 once invoked), scanned A, a copy of polish-docs-meta, Apache-2.0.

A final review for an MCP server, a program that lets AI tools access functions and data. It checks the server’s documentation and project metadata against what the code actually provides.

In plain words
What is it for?
Use it after tests and development checks pass, before a first commit, release, or public launch. It helps document the server’s functions, data access, inputs, outputs, and permission needs.
Why use it?
It removes the gap between working code and a repository that is ready to share or release. It also helps keep documentation accurate after tools, resources, or prompts change.

Skill for Claude Code

Written for Claude Code: Claude Code plugin machinery. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

Part of the finnhub-mcp-server plugin — 32 skills, 1 MCP server shipped together

Good fit Use it after tests and development checks pass, before a first commit, release, or public launch. It helps document the server’s functions, data access, inputs, outputs, and permission needs.

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

Made for: Claude Code.

Or install finnhub-mcp-server, the plugin that ships this one along with the rest of its 32 skills, 1 MCP server.

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/finnhub-mcp-server/polish-docs-meta/github.svg)](https://agentmods.dev/skills/cyanheads/finnhub-mcp-server/polish-docs-meta)
Your own site
<a href="https://agentmods.dev/skills/cyanheads/finnhub-mcp-server/polish-docs-meta"><img src="https://agentmods.dev/badge/skills/cyanheads/finnhub-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.

agentmods 80×15 button for polish-docs-meta

Your own site · 80×15
<a href="https://agentmods.dev/skills/cyanheads/finnhub-mcp-server/polish-docs-meta"><img src="https://agentmods.dev/badge/skills/cyanheads/finnhub-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 4,125 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 100% copy Near-identical to another mod 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.00054 $0.04125
Opus 5 $0.00027 $0.02063
Sonnet 5 $0.00011 $0.00825
Haiku 4.5 $0.00005 $0.00413

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

Origin

This is a copy

100% identical to polish-docs-meta — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

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

How it starts

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

  1. 12d ago First seen · 277 lines · 54 tokens per session scan A 50926cd53e50

Subscribe to this mod's changes

polish-docs-meta is a skill published in the GitHub repository cyanheads/finnhub-mcp-server (1 stars, last pushed 12d ago), licensed Apache-2.0. It adds 54 tokens to every session and 4,125 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to polish-docs-meta, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

ensembl-database

Query Ensembl genome database REST API for 250+ species. Gene lookups, sequence retrieval, variant analysis, comparative genomics, orthologs, VEP predictions, for genomic research.

synthetic-sciences/openscience · 45 tokens

colab-finetuning

Fine-tune LLMs on Google Colab GPUs directly from openscience. Connects to Colab runtimes via WebSocket bridge for remote training with Unsloth. Supports SFT, GRPO, DPO, vision, and TTS workflows on free T4 to Pro A100 GPUs.

synthetic-sciences/openscience · 67 tokens

crypto-market-rank

Crypto market rankings and leaderboards. Query trending tokens, top searched tokens, Binance Alpha tokens, tokenized stocks, social hype sentiment ranks, smart money inflow token rankings, top meme token rankings from Pulse launchpad, and top trader PnL leaderboards. Use this skill when users ask about token rankings…

tradecatlabs/tradecat-public · 85 tokens

simple-earn

Binance Simple-earn request using the Binance API. Authentication requires API key and secret key.

tradecatlabs/tradecat-public · 23 tokens

derivatives-trading-portfolio-margin-pro

Binance Derivatives-trading-portfolio-margin-pro request using the Binance API. Authentication requires API key and secret key.

tradecatlabs/tradecat-public · 33 tokens

trading-signal

Subscribe and retrieve on-chain Smart Money signals. Monitor trading activities of smart money addresses, including buy/sell signals, trigger price, current price, max gain, and exit rate. Use this skill when users are looking for investment opportunities — smart money signals can serve as valuable references for…

tradecatlabs/tradecat-public · 64 tokens