Claude Code: Everything You Need to Know is a practical guide to using Claude Code, an AI coding assistant that can be extended with commands, skills, hooks, subagents, workflows, and external tool servers. Developers use it to learn Claude Code from basic prompting through team and automation setups. The catalogue entries are examples of the guide's Claude Code extensions and workflows.
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 wesammustafa/Claude-Code-Everything-You-Need-to-Know --skill five-whysgit clone --depth 1 https://github.com/wesammustafa/Claude-Code-Everything-You-Need-to-KnowWrote 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/wesammustafa/claude-code-everything-you-need-to-know/five-whys)<a href="https://agentmods.dev/skills/wesammustafa/claude-code-everything-you-need-to-know/five-whys"><img src="https://agentmods.dev/badge/skills/wesammustafa/claude-code-everything-you-need-to-know/five-whys/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.
<a href="https://agentmods.dev/skills/wesammustafa/claude-code-everything-you-need-to-know/five-whys"><img src="https://agentmods.dev/badge/skills/wesammustafa/claude-code-everything-you-need-to-know/five-whys.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.00383 |
| Opus 5.5 | $0.00021 | $0.00153 |
| Sonnet 5.5 | $0.00011 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
five-whys 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 9d 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.
What it actually says
Find the root cause of this problem: $ARGUMENTS
If no problem is given, ask for one in a single sentence, then stop.
- Restate the problem as a symptom someone can observe: what happens, where and when.
- Ask "Why does this happen?" Answer from evidence: the code, tests, logs and git history. Mark any answer you can't back with evidence as a guess.
- Ask "Why?" of that answer, and keep going until the answer is a cause the team can change. That often takes about five rounds; stop sooner if you get there, and say so if you need more.
- Check the chain backwards: each cause must explain the step before it.
- Report the chain as a numbered list, the root cause in one sentence, then one fix for the root cause and one for the symptom.
Don't change any files. Propose the fixes and let the user decide.
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.
- 9d ago First seen · 24 lines · 53 tokens per session scan A 0dadec96f67b
five-whys is a skill published in the GitHub repository wesammustafa/Claude-Code-Everything-You-Need-to-Know (3,406 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 383 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-10-07.
Other skills, from other repositories
eval-hooks
Audit Claude Code and Codex hooks for validity, safety, and correctness across settings.json, hooks.json, config.toml, plugin, and skill or agent frontmatter hooks. Resolves each command, checks event names, handler types, matchers, exit-code and JSON decision strategy, and timeouts against each host's documented…
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
sandbox-unblock
Diagnostic protocol to run before reporting a sandbox blocker or asking for a configuration change. Eight checks that eliminate false positives, then a report template the person holding the settings can act on. On one measured day, six of eight reported blockers turned out to be false, all from the same handful of…
investigate
Systematic root-cause debugging: find the cause before writing any fix.
qa
Systematic QA testing of a web application: diff-aware, tiered, with fix-and-verify loop.
optimize
Analyze and suggest performance improvements for code, queries, or systems.