Borrowing it
Nothing to install: this file belongs to hamzafarooq/claude-code-starter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hamzafarooq/claude-code-starter/main/CLAUDE.mdgit clone --depth 1 https://github.com/hamzafarooq/claude-code-starterWrote 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/instructions/hamzafarooq/claude-code-starter/claude-md)<a href="https://agentmods.dev/instructions/hamzafarooq/claude-code-starter/claude-md"><img src="https://agentmods.dev/badge/instructions/hamzafarooq/claude-code-starter/claude-md.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.00650 | $0.00650 |
| Opus 5 | $0.00325 | $0.00325 |
| Sonnet 5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
claude-code-starter CLAUDE.md 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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code in Practice — Course Repo
What this repo is
Course materials for Claude Code in Practice (taught on Maven) — a hands-on course that teaches product managers to ship real things using Claude Code without relying on engineering.
- Audience: Product managers and non-engineers learning to build with Claude Code
- Status: Active (live cohorts running)
- Instructor: Hamza Farooq (Traversaal.ai, UCLA Anderson, ex-Google)
- Co-instructor: Aishwarya Ashok
- Maven course: https://maven.com/boring-bot/claude-code-in-practice
Repo structure
/
├── CLAUDE.md ← root context for Claude
├── README.md ← student-facing setup guide
├── primer.md ← course overview and navigation guide
├── memory.md ← decisions and module status log
├── LICENSE ← MIT
├── .claude/ ← Claude Code config (skills, commands, agents)
│ ├── skills/ ← all skill SKILL.md files (flat, one folder per skill)
│ ├── commands/ ← all slash command .md files
│ └── agents/ ← all sub-agent .md files
├── demos/ ← all runnable demo apps
│ ├── meeting-notes-summarizer/
│ ├── prd-generator/
│ ├── full-stack-demo/
│ ├── meetingmemo/
│ ├── skill-sub-multi-agent/
│ ├── research-agent/
│ ├── research-frontend/
│ ├── competitor-research-agent/
│ └── royal-pop-website/
├── docs/ ← reference resources
├── images/ ← screenshots and GIFs
└── bin/ ← npx installer CLI
Conventions
- Flat by type: skills in
.claude/skills/, agents in.claude/agents/, demos indemos/ - No module folders — content is organized by what it is, not which session it came from
- All skills and commands live at root
.claude/— no module-scoped subdirectories - Apps built live in class get their own GitHub repos (linked from root README)
- Version tags follow the pattern
v1.0,v2.0per release
How Claude should respond in this repo
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.
- 4d ago First seen · 64 lines · 650 tokens per session scan A 297419582bd3
claude-code-starter CLAUDE.md is an instructions file published in the GitHub repository hamzafarooq/claude-code-starter (141 stars, last pushed 1mo ago), licensed MIT. It adds 650 tokens to every session, about $0.0032 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-09-03.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.