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/rootwarp/claude-code-plugins-monorepo/python-docnpx skills add rootwarp/claude-code-plugins-monorepo --skill python-docgit clone --depth 1 https://github.com/rootwarp/claude-code-plugins-monorepoWhat 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.00000 | $0.00724 |
| Opus 5 | $0.00000 | $0.00362 |
| Sonnet 5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
python-doc 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/python-doc
Look up Python documentation from docs.python.org or PyPI.
Arguments
module: The Python module or package to look up (e.g.,asyncio,collections,requests)version(optional): Python version (e.g.,3.11). Defaults to3.symbol(optional): Specific function, class, or method to focus on
Instructions
When the user wants to verify or look up Python documentation:
Standard Library
-
Construct the URL based on the module:
- Base URL:
https://docs.python.org/3/library/ - With version:
https://docs.python.org/{version}/library/ - Example:
https://docs.python.org/3/library/asyncio.html
- Base URL:
-
Fetch the documentation using WebFetch with a prompt tailored to the user's needs.
Third-Party Packages (PyPI)
-
Construct the URL:
- PyPI:
https://pypi.org/project/{package}/ - Read the Docs:
https://{package}.readthedocs.io/(if available)
- PyPI:
-
Fetch the documentation using WebFetch.
URL Structure Reference
| Type | URL Format | Example |
|---|---|---|
| Stdlib | https://docs.python.org/3/library/{module}.html |
https://docs.python.org/3/library/asyncio.html |
| Stdlib with version | https://docs.python.org/{version}/library/{module}.html |
https://docs.python.org/3.11/library/typing.html |
| PyPI | https://pypi.org/project/{package}/ |
https://pypi.org/project/requests/ |
| Read the Docs | https://{package}.readthedocs.io/ |
https://requests.readthedocs.io/ |
Example Usage
Look up asyncio module
/python-doc asyncio
Fetches: https://docs.python.org/3/library/asyncio.html
Look up typing with specific version
/python-doc typing 3.11
Fetches: https://docs.python.org/3.11/library/typing.html
Look up third-party package
/python-doc requests
Fetches: https://pypi.org/project/requests/ and linked documentation
Execution
When invoked, use WebFetch to retrieve the documentation:
WebFetch url="https://docs.python.org/3/library/{module}.html" prompt="Extract the documentation for this Python module. Include: 1) Module overview 2) Key classes and functions 3) Common usage patterns 4) Code examples. If a specific symbol was requested, focus on that item's documentation."
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 · 82 lines · 0 tokens per session scan A 149c2fea15b7
python-doc is a skill published in the GitHub repository rootwarp/claude-code-plugins-monorepo (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 724 tokens. 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
coding-worktree-recovery
Use this skill when coding-agent work is interrupted, an agent exits without a clean commit, multiple controllers target the same checkout, or the checkout produces inconsistent file/Git behavior.
browser-harness-authoring
Use when mapping a repeatable website workflow into a verified Hermes skill so later runs can follow known steps instead of rediscovering the site. Surveys browser compatibility, semantic targets, failure modes, recovery paths, decision gates, and expiry using dummy data and no irreversible submissions.
obsidian-memory-architecture
Use when designing, setting up, or maintaining an Obsidian vault as Hermes Agent's durable knowledge layer. Routes facts, conversation history, documents, procedures, and daily logs to the correct Hermes or vault system without duplicating everything into the prompt.
cross-browser-typography-qa
Use this skill when web text looks clipped, flattened, wrapped incorrectly, misaligned, or materially different between Chromium and WebKit/Safari. Treat text rendering as both a geometry problem and a visual paint problem: passing DOM bounds does not prove that every glyph is intact.
hermes-diagnostic-review
Use when running a read-only diagnostic review of recent Hermes sessions to find recurring mistakes, failed tool calls, and repeated fixes, then propose suggestion-only improvements and reusable skills. Human-gated; never auto-applies.
inspecting-hermes-desktop-dom
When you are developing apps/desktop and the user is running that same app (hgui / npm run dev), you can read the live rendered DOM of the window they are looking at — computed styles, geometry, which CSS rule actually won, console output — instead of inferring it from .tsx and being wrong.