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 onboardgit 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/onboard)<a href="https://agentmods.dev/skills/wesammustafa/claude-code-everything-you-need-to-know/onboard"><img src="https://agentmods.dev/badge/skills/wesammustafa/claude-code-everything-you-need-to-know/onboard/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/onboard"><img src="https://agentmods.dev/badge/skills/wesammustafa/claude-code-everything-you-need-to-know/onboard.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.00056 | $0.00507 |
| Opus 5.5 | $0.00022 | $0.00203 |
| Sonnet 5.5 | $0.00011 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
onboard 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 6d 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
Explain this repository's shared Claude Code setup to a teammate who has just cloned it. Read files only; don't change any.
- Read the shared setup, skipping any file that doesn't exist:
.claude/settings.json: permissions, hooks, and the marketplaces and plugins it turns on;CLAUDE.mdand the files in.claude/rules/: the project's instructions to Claude;.claude/skills/and.claude/agents/: project skills and subagents;.mcp.json: project MCP servers;- each marketplace that
.claude/settings.jsondeclares by a local path, and the skills and agents of the plugins it lists.
- Name the personal files, which each teammate keeps out of the repository:
.claude/settings.local.json,CLAUDE.local.mdand the user folder~/.claude/. Don't open them. Say whether the repository's.gitignorelists the first two. - Report in three short sections: Shared with the team, Personal to you, and Added by team-kit. Give each file one line on what it does for the teammate. If a file you expected is missing, say so rather than guess what it would hold.
Keep the report short and concrete: file names and what each one changes, no general advice.
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.
- 6d ago First seen · 24 lines · 56 tokens per session scan A 70f6035c91b5
onboard is a skill published in the GitHub repository wesammustafa/Claude-Code-Everything-You-Need-to-Know (3,406 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 507 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-10.
Other skills, from other repositories
self-assessment
Interactive skill assessment with personalized learning path generation.
talk-stage5-script
Produces a complete 5-act pitch with speaker notes, a slide-by-slide specification, and a ready-to-paste Kimi prompt for AI slide generation. Requires validated angle and title from Stage 4. Use when you have a confirmed talk angle and need the full script, slide spec, and AI-generated presentation prompt.
talk-stage3-concepts
Builds a numbered, categorized concept catalogue from the talk summary and timeline, scoring each concept HIGH / MEDIUM / LOW for talk potential with optional repo enrichment. Use when you need a structured inventory of concepts before choosing a talk angle, or when assessing which ideas have the strongest…
talk-stage6-revision
Produces revision sheets with quick navigation by act, a master concept-to-URL table, Q&A cheat-sheet with 6-10 anticipated questions, glossary, and external resources list. Use when preparing for a talk with Q&A, creating shareable reference material for attendees, or building a safety-net glossary for live delivery.
explain
Explain code, concepts, or system behavior with adjustable depth levels.
learn-quiz
Test understanding of recently written or accepted code.