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/commands/wesammustafa/claude-code-everything-you-need-to-know/tdd)<a href="https://agentmods.dev/commands/wesammustafa/claude-code-everything-you-need-to-know/tdd"><img src="https://agentmods.dev/badge/commands/wesammustafa/claude-code-everything-you-need-to-know/tdd/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/commands/wesammustafa/claude-code-everything-you-need-to-know/tdd"><img src="https://agentmods.dev/badge/commands/wesammustafa/claude-code-everything-you-need-to-know/tdd.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.00015 | $0.01109 |
| Opus 5 | $0.00008 | $0.00554 |
| Sonnet 5 | $0.00003 | $0.00222 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
tdd 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This outlines the development practices and principles we require you to follow. Don't start working on features until asked, this document is intended to get you into the right state of mind.
- Make sure you are on the main branch before you start (unless instructed to start on a specific branch)
- Understand the code that is there before you begin to change it.
- Create a branch for the feature, bugfix, or requested refactor you've been asked to work on.
- Employ test-driven development. Red-Green-Refactor process (outlined below)
- When committing to git, omit the Claude footer from comments.
- Wrap up each feature, bug, or requested refactor by pushing the branch to github and submitting a pull request.
- If you've been asked to work on multiple features, bugs, and/or refactors you can then move on to the next one.
High-level flow
One vs many
Sometimes you will be given one task. Sometimes you will be given a task list. The list might be provided as a git repo issue list, for example.
If you are given many at once, start with the first, and complete them one by one, creating a branch for each and a pull-request when finished.
Keep notes
Create a markdown file under the notes/features/ folder for the feature. If you are creating a feature branch, use the same name.
Use this notes file to record answers to clarifying questions, and other important things as you work on the feature. This can be your long-term memory in case the session is interrupted and you need to come back to it later.
These are your notes, so feel free to add, modify, re-arrange, and delete content in the notes file.
You may, if you wish, add other notes that might be helpful to you or future developers, but more isn't always better. Be breif and helpful.
Understand the feature
- First read the README.md and any relevant docs it points to.
- Ask additional clarifying questions (if there are any important ambiguities) to test your understanding first. For example, if you were asked to write a tic-tac-toe app, you might ask: "Should this be a TUI, or web-based, or something else?"
- Update the README.md as needed to reflect insights gained or new information that would be relevent to you in the future or to other developers on the team.
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 · 79 lines · 15 tokens per session scan A 7cb0958f59f9
tdd is a command published in the GitHub repository wesammustafa/Claude-Code-Everything-You-Need-to-Know (2,981 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 1,109 once invoked, about $0.0001 per session on Opus 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-30.
Other commands, from other repositories
ccc-feature-start
Kickoff a new feature with branch creation, TDD setup, and task breakdown.
test
A command for running a project's automated tests, which are checks that software behaves as expected. It detects common project types and chooses a matching test command.
qa
A quality-assurance testing agent that checks whether software meets its stated acceptance requirements. It tests normal use, edge cases, failures, and regressions, then classifies the problems it finds.
verify
A command that runs a project's main quality checks in sequence: build, type checking, linting, tests, security scanning, and Git status checks. Linting checks code style and common mistakes; Git tracks file changes.
ccc-eval
Manage eval-driven development workflow — create, run, and track evals before writing implementation code.
ccc-tdd
Enforce test-driven development workflow. Scaffold interfaces, generate tests FIRST, then implement minimal code to pass. Ensure 80%+ coverage.