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.
git 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/agents/wesammustafa/claude-code-everything-you-need-to-know/test-gaps)<a href="https://agentmods.dev/agents/wesammustafa/claude-code-everything-you-need-to-know/test-gaps"><img src="https://agentmods.dev/badge/agents/wesammustafa/claude-code-everything-you-need-to-know/test-gaps/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/agents/wesammustafa/claude-code-everything-you-need-to-know/test-gaps"><img src="https://agentmods.dev/badge/agents/wesammustafa/claude-code-everything-you-need-to-know/test-gaps.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.00038 | $0.00128 |
| Opus 5.5 | $0.00015 | $0.00051 |
| Sonnet 5.5 | $0.00008 | $0.00026 |
| Haiku 4.5 | $0.00004 | $0.00013 |
Grade A, and why
test-gaps 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 today.
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
You find code that no test exercises. You never change files.
- List the functions each source file exports.
- For each one, search the test files for a call to it.
- Report the functions that no test calls, grouped by file, with one line on what a test for each should check. If every function has a test, say so.
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.
- today First seen · 12 lines · 38 tokens per session scan A 4e517ded07fc
test-gaps is an agent published in the GitHub repository wesammustafa/Claude-Code-Everything-You-Need-to-Know (3,516 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 128 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-11-01.
Other agents, from other repositories
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
orc-test-author
Executor role — designs and writes test suites for new or changed behaviour: edge cases, error paths, fixtures. Used by /orc:debug (regression test), /orc:flow Phase 4 (first failing test) and /orc:qa.
debugger
Root-cause debugging: reproduce, confirm the cause with evidence, apply a minimal fix and prove it with a regression test. Use for bugs, flaky tests or errors of unknown cause.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.
creo-unit-test
Unit and integration test specialist using Vitest, Jest, and Testing Library for components, hooks, and stores.
tdd-guide
A testing guide for test-driven development, a method where developers write a failing test before writing the code that should pass it.