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.
npx skills add cyanheads/medical-codes-mcp-server --skill setupgit clone --depth 1 https://github.com/cyanheads/medical-codes-mcp-serverWrote 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/cyanheads/medical-codes-mcp-server/setup)<a href="https://agentmods.dev/skills/cyanheads/medical-codes-mcp-server/setup"><img src="https://agentmods.dev/badge/skills/cyanheads/medical-codes-mcp-server/setup.svg" alt="Measured on agentmods" 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.00058 | $0.02458 |
| Opus 5 | $0.00029 | $0.01229 |
| Sonnet 5 | $0.00012 | $0.00492 |
| Haiku 4.5 | $0.00006 | $0.00246 |
Grade A, and why
setup scanned grade A with 1 finding 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 6d 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.
Asks the agent to reveal its instructionslowSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
1. **Clean up what you don't need.** If your server has no prompts, delete the echo prompt and its registration in `src/index.ts`. Same for resources, or the app-tool pair if you're not targeting UI-capable clients. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
This is a copy
100% identical to setup — 16 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
This skill assumes bunx @cyanheads/mcp-ts-core init [name] has already run. The CLI created the project's CLAUDE.md and AGENTS.md for different agents, copied external skills to skills/, and scaffolded the directory structure with echo definitions as starting points. This skill covers what was created and what to do next.
Agent Protocol File
The init CLI generates both CLAUDE.md and AGENTS.md with identical content — CLAUDE.md is read by Claude Code, AGENTS.md by Codex, Cursor, Windsurf, and other agents. Keep both. Shipping both keeps the project agent-agnostic, and they're cheap to hold in sync: edit one, then cp CLAUDE.md AGENTS.md (the framework keeps its own pair byte-identical the same way, enforced by check-docs-sync). Only delete one if you're certain the project will never be opened by the other family of agents.
For the full framework docs, read node_modules/@cyanheads/mcp-ts-core/CLAUDE.md (or its identical twin AGENTS.md) once per session. It contains the exports catalog, tool/resource/prompt contracts, error codes, context API, and common import patterns.
Project Structure
What init actually creates:
CLAUDE.md # Agent protocol — Claude Code
AGENTS.md # Agent protocol — other agents (Codex, Cursor, etc.)
package.json # Starter deps + scripts (placeholders substituted on init)
tsconfig.json # Typecheck config — covers src/ and tests/, emits nothing
tsconfig.build.json # Build config — emits src/ to dist/, tests excluded
vitest.config.ts # Test runner config
biome.json # Lint + format config
devcheck.config.json # Which devcheck steps to run
Dockerfile # Starter multi-stage image
.dockerignore
.env.example # Copy to .env and fill in
.gitignore
.github/ISSUE_TEMPLATE/ # Bug / feature-request issue forms
.vscode/ # Recommended extensions + editor settings
server.json # MCP Registry publishing metadata
changelog/template.md # Format reference for per-version changelog files
scripts/ # build, clean, devcheck, lint-mcp, list-skills, build-changelog, tree, check-docs-sync
skills/ # External skills copied from the package (source of truth)
src/
index.ts # createApp() entry point
mcp-server/
tools/definitions/
echo.tool.ts # Standard tool starter
echo-app.app-tool.ts # UI-enabled app tool starter (pairs with echo-app-ui resource)
resources/definitions/
echo.resource.ts # Standard resource starter
echo-app-ui.app-resource.ts # UI resource paired with echo-app app tool
prompts/definitions/
echo.prompt.ts # Prompt starter
tests/
tools/echo.tool.test.ts # Starter tests (one per echo definition)
resources/echo.resource.test.ts
prompts/echo.prompt.test.ts
smoke/definitions.smoke.test.ts # Every shipped definition executed once
integration/echo-contract.int.test.ts # The echo tool driven through the production surfaces
fuzz/echo-tool.fuzz.test.ts # Property-based coverage, via the fast-check dev dep
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.
- 6d ago First seen · 167 lines · 58 tokens per session scan A 518e037129fb
setup is a skill published in the GitHub repository cyanheads/medical-codes-mcp-server (2 stars, last pushed 12d ago), licensed Apache-2.0. It adds 58 tokens to every session and 2,458 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (asks the agent to reveal its instructions). It is 100% identical to setup, differing in 16 lines, and is treated as a copy.
Other skills, from other repositories
tool-prompt-optimization
Optimize the description prompts an AI agent reads to learn its built-in tools (the .md files under prompts/tools/). Two halves: (1) measure how much of a prompt is already inferable from the tool's JSON parameter schema + name, to prune redundancy with evidence; (2) house authoring rules for what belongs in a tool…
semantic-compression
Re-encode verbose prose into a dense telegraphic register — punctuation as connectives, label frames, verbless assertions — without losing normativity or precision. Use when compressing system prompts, tool/function descriptions, skill bodies, or agent instructions; reducing token count or context bloat; making…
auditing-part11-trails
Generates and verifies 21 CFR Part 11-style audit trails — who/what/when, electronic signatures, and tamper-evidence — for OpenMed pipelines in GxP and clinical-trial (GCP) settings. Use when the user runs OpenMed in a regulated/validated environment and needs an attributable, time-stamped, tamper-evident record of…
batch-processing-clinical-text
Run large-scale batch NER, PII extraction, or de-identification over many clinical notes on-device with OpenMed, with sharding, checkpointing, resumability, and append-only JSONL output. Use when the user needs to process a corpus or folder of notes, de-identify a dataset, run NER over thousands of documents, build a…
coding-hcc-risk-adjustment
Maps chronic conditions extracted by OpenMed to CMS-HCC V28 risk-adjustment categories and estimates a RAF (Risk Adjustment Factor) score as decision support. Use when the user wants to surface risk-adjustable diagnoses from notes, map ICD-10-CM codes to HCC categories, estimate or reconcile a patient/panel RAF, find…
detecting-pv-signals
Computes disproportionality signals — PRR, ROR, EBGM, and IC (BCPNN) — over FAERS / OpenFDA drug-event data to flag potential safety signals. Use when the user wants to mine spontaneous-report data for drug-reaction associations, build a 2x2 contingency table, compute a Proportional Reporting Ratio or Reporting Odds…