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 skills add PaulRBerg/agent-skills --skill agents-docsgit clone --depth 1 https://github.com/PaulRBerg/agent-skillsWrote 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/paulrberg/agent-skills/agents-docs)<a href="https://agentmods.dev/skills/paulrberg/agent-skills/agents-docs"><img src="https://agentmods.dev/badge/skills/paulrberg/agent-skills/agents-docs.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.01686 |
| Opus 5 | $0.00028 | $0.00843 |
| Sonnet 5 | $0.00011 | $0.00337 |
| Haiku 4.5 | $0.00006 | $0.00169 |
Grade A, and why
agents-docs scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Requires curl and a writable user cache directory; network populates or refreshes fixed artifacts and fetches uncached How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents Docs
This skill is coordination-exempt: skip the ai-coord gate for its declared work.
Supported Chat Hosts
Before doing any work, identify the current chat host. If it is not Claude Code or Codex CLI, stop with this error:
This skill only works in Claude Code or Codex CLI.
Answer Codex and Claude Code product questions from the narrowest relevant official documentation.
Classify the request
Classify the request as Codex, Claude Code, or a comparison. Use this skill only for those products and their documented behavior; route generic agent work and provider API, SDK, pricing, authentication, model, migration, or managed-agent questions to their relevant source.
Treat $imagegen and Codex image-prompting questions as Codex product questions even when detailed supporting model
guidance lives in OpenAI's API Cookbook.
Route official sources
- For Codex, start only at
https://developers.openai.com. Resolvescripts/fetch-doc.shrelative to this skill directory, runfetch-doc.sh codex-manual, search the returned path narrowly withrg, and read only the matching heading range into context. The fixed manual and schema endpoints may redirect to their exacthttps://learn.chatgpt.com/docs/counterparts. - For
$imagegenand Codex image-prompting questions, read the manual's exact Image generation topic first. When detailed prompting patterns or production examples are needed, also read the GPT Image Generation Models Prompting Guide. Apply its prompt-writing guidance to$imagegen, but treat model selection, flags, and API parameters as API-only unless Codex documentation confirms the built-in skill exposes them. - For Claude Code, use only
https://code.claude.com. Start broad product research athttps://code.claude.com/docs/en/overview.md. - For Codex, accept a
cachedmanual for ordinary product questions. Use--refreshfor release/change questions, materially disputed freshness, schema/config discrepancies, conflicts with observed local behavior, and other explicitly unstable cases. - When the Codex manual contains sufficient supporting text and identifies the final topic-specific official URL, answer from that evidence and cite the topic URL. When it identifies the topic page but lacks enough detail, fetch that exact Markdown page directly. Run one compact domain-restricted search only when the exact official page remains unknown. Never search merely to rediscover a URL already identified by the manual.
- For a specific Claude Code topic, run a compact domain-restricted web search for the exact official page, then fetch its Markdown representation when available. Retrieve only the page or section needed for the answer; never fetch a complete documentation inventory as a discovery shortcut.
- Prefer the current client's URL-capable fetch for narrow topic pages. Use the helper only for its two fixed Codex artifacts.
- For comparisons, complete both provider routes independently. Never infer one product's behavior from the other's documentation.
What ships with it
3 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.
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.
- 8d ago First seen · 132 lines · 55 tokens per session scan A ab6ded75863c
agents-docs is a skill published in the GitHub repository PaulRBerg/agent-skills (70 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,686 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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-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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…