claude-code-docs

claude-code-docs is a skill for Claude Code from AnswerDotAI/skill-plugins. It costs 44 tokens per session (344 once invoked), scanned A, original, Apache-2.0.

A skill for answering questions about Claude Code, the command-line coding assistant, using its current official documentation.

In plain words
What is it for?
Use it when explaining or troubleshooting Claude Code features, configuration, CLI behavior, hooks, skills, plugins, permissions, sessions, or compaction.
Why use it?
Claude Code’s commands, settings, permissions, hooks, plugins, and session behavior can change. The skill directs the agent to find and use the relevant official documentation.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the claude-aai plugin — 5 skills shipped together

Good fit Use it when explaining or troubleshooting Claude Code features, configuration, CLI behavior, hooks, skills, plugins, permissions, sessions, or compaction.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/answerdotai/skill-plugins/claude-code-docs
Install

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.

Any agent
npx skills add AnswerDotAI/skill-plugins --skill claude-code-docs
Clone the repo
git clone --depth 1 https://github.com/AnswerDotAI/skill-plugins

Made for: Claude Code.

Or install claude-aai, the plugin that ships this one along with the rest of its 5 skills.

Wrote 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.

agentmods badge for claude-code-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/answerdotai/skill-plugins/claude-code-docs/github.svg)](https://agentmods.dev/skills/answerdotai/skill-plugins/claude-code-docs)
Your own site
<a href="https://agentmods.dev/skills/answerdotai/skill-plugins/claude-code-docs"><img src="https://agentmods.dev/badge/skills/answerdotai/skill-plugins/claude-code-docs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for claude-code-docs

Your own site · 80×15
<a href="https://agentmods.dev/skills/answerdotai/skill-plugins/claude-code-docs"><img src="https://agentmods.dev/badge/skills/answerdotai/skill-plugins/claude-code-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 344 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.00344
Opus 5.5 $0.00018 $0.00138
Sonnet 5.5 $0.00009 $0.00069
Haiku 4.5 $0.00004 $0.00034

Measured 1mo ago against content hash 9fd17f0424fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

claude-code-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 1mo 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.

plugins/claude-aai/skills/claude-code-docs/SKILL.md · 14 lines

What it actually says

Claude Code Docs

  1. Work in clikernel. Fetch https://code.claude.com/docs/llms.txt exactly with httpx, save its text to a variable, and display the whole variable. It is the table of contents agents are meant to inspect.
  2. Choose the link whose title matches the question. Do not replace the requested URL with a similar page.
  3. Fetch that linked Markdown page with httpx and save its text to another variable. Never fetch llms-full.txt; select the relevant page from llms.txt instead.
  4. Check the Markdown page's len(). If it is at most 30,000 characters, display the whole page. If it is larger, do not display it: load the toolslm.read_md pyskill, parse the page variable, inspect paths(), and retrieve the relevant sections. Fetch shared sections separately when an event-specific section refers to them.
  5. Use the official documentation for documented interfaces and normal day-to-day behavior. Claude Code ships no public source; when the docs do not answer the question, check the changelog and What's New pages for recent changes, and investigate observed behavior directly (settings files, --help, /doctor).
  6. Base the answer on the strongest applicable evidence: documented contracts for public behavior, and direct observation for runtime behavior. Distinguish among them when it matters.
Changes

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.

  1. 1mo ago First seen · 14 lines · 44 tokens per session scan A 9fd17f0424fb

Subscribe to this mod's changes

claude-code-docs is a skill published in the GitHub repository AnswerDotAI/skill-plugins (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 344 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens