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/nrl-ai/chub/get-api-docsnpx skills add nrl-ai/chub --skill get-api-docsgit clone --depth 1 https://github.com/nrl-ai/chubWrote 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/nrl-ai/chub/get-api-docs)<a href="https://agentmods.dev/skills/nrl-ai/chub/get-api-docs"><img src="https://agentmods.dev/badge/skills/nrl-ai/chub/get-api-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 | $0.00094 | $0.00830 |
| 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 3d 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.
This is a copy
100% identical to get-api-docs — 1 line 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 — 90 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.
- 3d ago First seen · 90 lines · 94 tokens per session scan A 441876d81988
get-api-docs is a skill published in the GitHub repository nrl-ai/chub (11 stars, last pushed 5mo ago), licensed MIT. It adds 94 tokens to every session and 830 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to get-api-docs, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
repomix
Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.
flux-analyzer
Analyse FBA flux distributions to extract biological insights. Covers gene essentiality, phenotypic phase planes, flux sampling, pathway-level aggregation, secretion product prediction, and production of publication- quality figures.
statistical-method-design
Design statistical methods, baselines, diagnostics, variants, and ablations that directly address a formal problem formulation.
experimental-design
Best practices for designing reproducible ML experiments. Use when planning ablations, baselines, or controlled experiments.
meta-harness
Run one iteration of memory system evolution. Called by metaharness.py or interactively via /meta-harness.
prolong
Recover and use durable coding-session history from PRO-LONG's local append-only log. Use on long-running coding tasks, after context compaction or session resume, when reconstructing prior decisions or tool results, or before repeating work that may already have been attempted.