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/nick-railsback/skill-engine/modelcontextprotocol-python-sdk-contextnpx skills add nick-railsback/skill-engine --skill modelcontextprotocol-python-sdk-contextgit clone --depth 1 https://github.com/nick-railsback/skill-engineWhat 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 | $0.00116 | $0.02443 |
| Opus 5 | $0.00058 | $0.01222 |
| Sonnet 5 | $0.00023 | $0.00489 |
| Haiku 4.5 | $0.00012 | $0.00244 |
Grade A, and why
modelcontextprotocol-python-sdk-context 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context navigator
Overview
This navigator catalogs references for the official MCP Python SDK at GitHub SHA 3eb579948a4719d606d2adbd1f3f69371c9c0f48 (HEAD of main on 2026-05-26). HEAD is v2 pre-alpha; the current stable release lives on the v1.x branch and uses the older FastMCP / camelCase / decorator-based APIs. All references in this contextualizer document v2 syntax — if you have v1 code in front of you, start with the migration reference.
When asked a question this navigator's domain covers:
- Scan the Catalog below for the matching topic.
- Follow the link to read the reference file.
- If the question spans multiple references, consult the Cross-reference map.
- If a reference points at a source URL for deeper detail, follow it only if the reference itself didn't answer the question.
Claims policy
Cite by default, and make load-bearing claims verifiable:
- Inline-cite every load-bearing claim with its SHA-pinned permalink — the
https://github.com/<owner>/<repo>/blob/<sha>/<path>#L<start>-L<end>link the reference gives for that fact (versions, defaults, signatures, deprecations, behavior a user could get wrong by guessing). Put the permalink inline, on the claim. Use a bare filename parenthetical (e.g. (reference-name.md)) only when the reference genuinely provides no permalink. This inline permalink is what the grounded-citation eval (SELF-AUDIT Check 8) grades. - Don't cite orientational prose — "what is X?", "when did X launch?" — answer those from this navigator alone; opening a reference is itself a citation gesture.
- End with a one-line provenance footer, emitted italic, formatted
*References consulted: foo.md, bar.md. Grounded in {{LIBRARY}}@{{VERSION}} — [reference index]({{INDEX_URL}}).*The footer is a summary of what you read — not a substitute for the inline permalinks on the claims. The{{LIBRARY}}/{{VERSION}}/{{INDEX_URL}}tokens are agent-substituted at answer time, so they appear literally in the stampedSKILL.md. - If no reference was opened, say so in the footer ("Answered from general knowledge — no {{LIBRARY}} references consulted") — never fake it.
What ships with it
20 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.
- references/modelcontextprotocol-python-sdk-auth.md 12 KB
- references/modelcontextprotocol-python-sdk-client.md 11 KB
- references/modelcontextprotocol-python-sdk-experimental-tasks.md 12 KB
- references/modelcontextprotocol-python-sdk-lowlevel-server.md 11 KB
- references/modelcontextprotocol-python-sdk-mcpserver.md 12 KB
- references/modelcontextprotocol-python-sdk-migration-v1-to-v2.md 17 KB
- references/modelcontextprotocol-python-sdk-overview.md 8.8 KB
- references/modelcontextprotocol-python-sdk-transports.md 12 KB
- references/modelcontextprotocol-python-sdk-types.md 9.7 KB
- research/.discover-cache.json 186 B
- research/.engine-stats.json 476 B
- research/.research-state.json 22 B
- research/eval-prompts-test.json 979 B
- research/eval-prompts-train.json 1.5 KB
- research/eval-results.md 4.5 KB
- research/review-state.json 97 B
- research/sessions/self-audit-2026-05-19.json 740 B
- research/sessions/self-audit-2026-05-26.json 485 B
- research/source-paths.json 483 B
- verify.sh 61 KB runs code
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 First seen · 90 lines · 116 tokens per session scan A 84f2e5960927
modelcontextprotocol-python-sdk-context is a skill published in the GitHub repository nick-railsback/skill-engine (2 stars, last pushed 24d ago), licensed MIT. It adds 116 tokens to every session and 2,443 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
skill-creator
Create or improve Zhin Agent skills (SKILL.md). Use when asked to add a skill, write SKILL.md, document a repeatable agent workflow, or refine skill frontmatter/keywords. Triggers: 创建技能, 写 SKILL, skill-creator, 加 skill.
skill-sync-checker
Detects content drift between skill files and their source documents. Helps maintain skills that are derived from other documentation by comparing content and flagging outdated sections.
tech-design-generation
Generates professional Technical Design Documents following industry-standard engineering practices. This skill activates when the user asks to write a technical design, create an architecture design, draft a design doc, write a technical proposal, do system design, create a technical design document, write an RFC…
test-cases-generation
Generates structured test case sets with multi-dimensional coverage from project code analysis or specification documents. This skill activates when the user asks to write test cases, generate tests, supplement tests, create test coverage, or improve test completeness. It auto-scans the project to extract testable…
idea
Use when exploring a new idea before writing formal specifications. Guides users through iterative discovery, research, and critical analysis to crystallize vague ideas into validated requirement drafts. Includes anti-pseudo-requirement checks, competitive research, demand evidence gathering, and "What if we don't…
test-plan-generation
Generates professional Test Plan and Test Cases documents following IEEE 829 test documentation standards, ISTQB testing methodologies, and Google Testing Blog best practices. This skill activates when the user asks to write a test plan, create test cases, draft a test plan document, create a test cases document…