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/thangchung/agent-engineering-experiment/get-api-docsnpx skills add thangchung/agent-engineering-experiment --skill get-api-docsgit clone --depth 1 https://github.com/thangchung/agent-engineering-experimentWhat 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.00094 | $0.00829 |
| Opus 5 | $0.00047 | $0.00415 |
| Sonnet 5 | $0.00019 | $0.00166 |
| Haiku 4.5 | $0.00009 | $0.00083 |
Grade A, and why
get-api-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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- get-api-docs — 100% identical, 1 lines differ
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get API Docs via chub
When you need documentation for a library or API, fetch it with the chub CLI
rather than guessing from training data. This gives you the current, correct API.
Step 1 — Find the right doc ID
chub search "<library name>" --json
Pick the best-matching id from the results (e.g. openai/chat, anthropic/sdk,
stripe/api). If nothing matches, try a broader term.
Step 2 — Fetch the docs
chub get <id> --lang py # or --lang js, --lang ts
Omit --lang if the doc has only one language variant — it will be auto-selected.
Step 3 — Use the docs
Read the fetched content and use it to write accurate code or answer the question. Do not rely on memorized API shapes — use what the docs say.
Step 4 — Annotate what you learned
After completing the task, if you discovered something not in the doc — a gotcha, workaround, version quirk, or project-specific detail — save it so future sessions start smarter:
chub annotate <id> "Webhook verification requires raw body — do not parse before verifying"
Annotations are local, persist across sessions, and appear automatically on future
chub get calls. Keep notes concise and actionable. Don't repeat what's already in
the doc.
Step 5 — Give feedback
Always rate the doc after using it. This helps authors fix outdated or incorrect docs and prioritize improvements. Include a label and a brief comment explaining what was good or what needs fixing — specific feedback is the most valuable.
chub feedback <id> up --label accurate "Clear examples, models are current"
chub feedback <id> down --label outdated "Lists gpt-4o as latest but gpt-5.4 is out"
Available labels: outdated, inaccurate, incomplete, wrong-examples,
wrong-version, poorly-structured, accurate, well-structured, helpful,
good-examples.
If you notice the doc has wrong model names, deprecated APIs, missing features, or incorrect code patterns, always leave a downvote with details so it can be fixed.
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.
- 2d ago First seen · 89 lines · 94 tokens per session scan A 8d1e05e24390
get-api-docs is a skill published in the GitHub repository thangchung/agent-engineering-experiment (24 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 829 once invoked, about $0.0005 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-30.
Other skills, from other repositories
phoenix-cli
Debug LLM applications using the Phoenix CLI. Fetch traces, analyze errors, structure trace review with open coding and axial coding, inspect datasets, review experiments, query annotation configs, and use the GraphQL API. Use whenever the user is analyzing traces or spans, investigating LLM/agent failures, deciding…
phoenix-github
Manage GitHub issues, labels, project boards, sprint operations, and roadmap health for the Arize-ai/phoenix repository. Use when filing roadmap issues, triaging bugs, applying labels, running sprint close-out and rollover, auditing board hygiene, checking ticket-load balance across the team, keeping roadmap epics up…
pxi-eval-dataset
Generate synthetic evaluation datasets for the PXI eval harness (evals/pxi/). Use whenever the user asks to create, author, draft, expand, or audit an eval dataset for a PXI tool, skill, or behavior — including phrases like "write evals for ", "test PXI behavior", "synthetic dataset for PXI", "cover this tool with…
phoenix-docs-gap-audit
Audit documentation gaps across the Phoenix repo by analyzing recent commits to main (default: last 7 days). Use this skill whenever the user asks to find undocumented features, identify docs gaps, audit what shipped without docs, check which recent changes need documentation, review stale docs against current code…
phoenix-release-notes
Create Phoenix release documentation grounded in actual code changes. Use this skill whenever the user asks to write release notes, document a release, update release documentation, or mentions undocumented releases. Also trigger when the user wants to update GitHub release descriptions, add entries to the release…
phoenix-skills-audit
Audit recent changes to Phoenix's user-facing surfaces (Python clients, TypeScript clients, CLI, REST/GraphQL APIs) and patch the three external-facing agent skills — phoenix-tracing, phoenix-cli, and phoenix-evals — so they stay in sync with what actually shipped. Use this skill whenever a user asks to update those…