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 agentmods add skills/neschadin/askell-mcp/mcp-docsnpx skills add Neschadin/askell-mcp --skill mcp-docsgit clone --depth 1 https://github.com/Neschadin/askell-mcpWrote 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/neschadin/askell-mcp/mcp-docs)<a href="https://agentmods.dev/skills/neschadin/askell-mcp/mcp-docs"><img src="https://agentmods.dev/badge/skills/neschadin/askell-mcp/mcp-docs.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.00113 | $0.00958 |
| Opus 5 | $0.00056 | $0.00479 |
| Sonnet 5 | $0.00023 | $0.00192 |
| Haiku 4.5 | $0.00011 | $0.00096 |
Grade A, and why
mcp-docs 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP live docs (protocol + TS SDK v2)
Spec and SDK move faster than training data. Live docs beat memory. This project is already an MCP v2 stdio server (@modelcontextprotocol/server, serveStdio, registerTool). Do not scaffold a new server (that is typescript-mcp-server-generator). Do not re-design the tool catalog (that is mcp-tool-design).
Sources
| What | Index | How to read |
|---|---|---|
| Protocol, Inspector, security | https://modelcontextprotocol.io/llms.txt | MCP tools first, then fetch page .md URLs |
| TypeScript SDK v2 (2026-07-28) | https://ts.sdk.modelcontextprotocol.io/v2/llms.txt | Fetch index, then the page's .md URL |
Every SDK page is also plain markdown at the same path with .md (e.g. tools). Full dump: https://ts.sdk.modelcontextprotocol.io/v2/llms-full.txt — only if you need many pages at once.
Prefer 2026-07-28 (and docs/2026-07-28/…). Ignore older spec eras in the protocol llms.txt unless the user names one.
Fetch strategy
Protocol — MCP tools first
If search_model_context_protocol is connected:
search_model_context_protocol({ query })- Read the page with
query_docs_filesystem_model_context_protocol(head/catthe.mdxpath). Do not treat that tool as a real shell.
Fallback if those tools are missing:
- Fetch https://modelcontextprotocol.io/llms.txt
- Pick the 2026-07-28 (or
specification/2026-07-28) URL - Fetch that
.mdURL
TypeScript SDK v2
- If Context7 is available:
resolve-library-idthenquery-docswith library/websites/ts_sdk_modelcontextprotocol_io_v2(or/modelcontextprotocol/typescript-sdk). - Else fetch https://ts.sdk.modelcontextprotocol.io/v2/llms.txt, pick the page, fetch its
.mdURL.
Quick map (SDK v2):
- Tools /
registerTool→servers/tools.md - Resources →
servers/resources.md - Prompts →
servers/prompts.md - Completion →
servers/completion.md - Logging, progress, cancel →
servers/logging-progress-cancellation.md - Elicitation →
servers/elicitation.md input_required(not sunset sampling) →servers/input-required.md- Errors →
servers/errors.md - stdio /
serveStdio→serving/stdio.md - Testing →
testing.md - v1 → v2 →
migration/upgrade-to-v2.md - 2026-07-28 protocol on v2 packages →
migration/support-2026-07-28.md
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.
- yesterday Changed · +7 tokens per session 21185f090ff2
- 4d ago First seen · 75 lines · 106 tokens per session scan A f8c2febced73
mcp-docs is a skill published in the GitHub repository Neschadin/askell-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 113 tokens to every session and 958 once invoked, about $0.0006 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…