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 imMamdouhaboammar/get-fable --skill claude-code-docsgit clone --depth 1 https://github.com/imMamdouhaboammar/get-fableWrote 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/immamdouhaboammar/get-fable/claude-code-docs)<a href="https://agentmods.dev/skills/immamdouhaboammar/get-fable/claude-code-docs"><img src="https://agentmods.dev/badge/skills/immamdouhaboammar/get-fable/claude-code-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.1 | $0.00021 | $0.01263 |
| Opus 5 | $0.00010 | $0.00632 |
| Sonnet 5 | $0.00004 | $0.00253 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade B, and why
claude-code-docs scanned grade B 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Show where the setting goes (`~/.claude/settings.json` vs `.claude/settings.json` vs `.mcp.json` vs `--flag`). How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Configuration Guide
You are answering a question about Claude Code itself: its commands, flags, settings, hooks, skills, MCP servers, subagents, IDE integrations, sandboxing, or any other part of how Claude Code works or is configured.
Your knowledge of Claude Code is stale by default
Claude Code changes frequently. Commands are added, renamed, and removed. Flags change. Settings keys move. The information in your training data about Claude Code is from a snapshot and may be wrong about what exists right now.
Before you tell the user about a slash command, CLI flag, settings key, hook event, or any other Claude Code surface:
- Check the live configuration in this prompt first. The "Current Build" section below is generated from the running binary at the moment you were invoked. It is ground truth. If a slash command isn't in that list, it doesn't exist in this build, no matter what you remember.
- Check the bundled references.
references/recent-changes.mdlists features that were renamed or removed since common training cutoffs.references/live-sources.mdmaps topics to documentation URLs. - Fetch the documentation if you can. Use WebFetch with a URL from
references/live-sources.md. If the user is asking about something not in the live config and not in the bundled references, fetch the docs map athttps://code.claude.com/docs/en/claude_code_docs_map.mdto find the right page, then fetch that page. - If you cannot reach the network, say so. Do not silently answer from training data. Say something like: "I can't reach the documentation right now. Based on my training data, [answer], but this may be out of date — check https://code.claude.com/docs for the current behavior."
When your training data disagrees with the live configuration or the bundled references, the live configuration and bundled references win. When it disagrees with fetched documentation, the documentation wins.
How to find the answer
| The user is asking about… | Check |
|---|---|
| A slash command | The "Available commands" list in Current Build below |
| A CLI flag | references/live-sources.md → CLI reference URL, or claude --help |
| A settings key | The "Settings keys configured" list in Current Build below, then the Settings docs |
| A hook event or hook config | references/live-sources.md → Hooks URL |
| An MCP server | The "Configured MCP servers" list in Current Build below, then the MCP docs |
| A custom skill or subagent | The "Custom skills/agents" lists in Current Build below |
| A keyboard shortcut | references/live-sources.md → Interactive mode URL |
Rebinding keys / ~/.claude/keybindings.json |
The keybindings entry in references/recent-changes.md § Commonly misremembered behavior, then the Interactive mode URL |
| What changed recently | The "Recent releases" section in Current Build below, then references/recent-changes.md for removals/renames |
Claude in Slack / Claude Tag / @Claude in Slack / /install-slack-app |
references/claude-tag.md, then the docs page |
| Anything else about Claude Code | The docs map URL, then the specific page |
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 · 62 lines · 21 tokens per session scan B 60e993ba0bdd
claude-code-docs is a skill published in the GitHub repository imMamdouhaboammar/get-fable (3 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 1,263 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
brainstorming
Use this BEFORE any creative or feature work: building a new feature, adding functionality, changing behavior, or making a nontrivial design decision. Turns the user's request into a validated design — recorded as a spec-graph task-spec — before any implementation. Do not skip this because a change looks small.
reviewing-changes
Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with addreviewcomment, and settle with exactly one reviewverdict.
spec-graph
The project's specs are its ground truth: durable documents describing the architecture, decisions, contracts, and boundaries behind the code, organized as a connected graph. Read this skill and reach for the spec tools FIRST — before reading code — whenever you explore the project, plan or start a task, add or change…