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 agentmods add instructions/digitalboutique-ai/hackerx/claude-mdgit clone --depth 1 https://github.com/DigitalBoutique-ai/hackerxWrote 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/digitalboutique-ai/hackerx/claude-md)<a href="https://agentmods.dev/instructions/digitalboutique-ai/hackerx/claude-md"><img src="https://agentmods.dev/badge/instructions/digitalboutique-ai/hackerx/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.00737 | $0.00737 |
| Opus 5 | $0.00368 | $0.00368 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
hackerx 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 5d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HackerX — Project Conventions
This is the working directory for the HackerX product (formerly Vibe Coder 100x). When Claude Code is invoked here, it should behave as the course teaches — not as a generic assistant.
The product surface is hackerx.app. This monorepo contains:
- Course markdown (
00-start-here/…11-final-operating-system/,templates/) — the canonical source of truth. site/— the Astro Starlight site that powers hackerx.app. Reads fromsite/course/(a build-time copy of the canonical content).cli/— thehackerxnpm CLI + Claude Code plugin.scripts/sync-course-to-site.sh— copies the canonical course modules intosite/course/after edits.
When you change course markdown at the repo root, also run scripts/sync-course-to-site.sh so the site rebuild picks up the change.
Behavior rules
- This repo contains course content, not a deployable app. Do not scaffold React/Vite/Next unless explicitly asked.
- All content lives in markdown. Prefer editing existing files over creating new ones.
- Numbered folder prefixes (
00-,01-, ...) are intentional — preserve them so the course stays ordered. - Cross-link aggressively. Every module's
README.mdshould link to its siblings. - When adding a new lesson, also add it to the top-level README.md course map.
Voice and tone
- Punchy, second-person ("you do this, then you do that").
- No corporate hedging. Direct over diplomatic.
- Show prompts as code blocks so they're copy-pasteable.
- Every "weak prompt" should have a "better prompt" right next to it.
- No emojis unless explicitly requested.
Structure rules for lessons
Every lesson should answer:
- What's the problem this solves? (one sentence)
- What's the pattern / prompt / vocabulary? (the actual content)
- When do you use it? (decision criteria)
- What's a weak vs. better prompt? (concrete example)
- What does Claude Code verify? (typecheck, lint, responsive, a11y, screenshot)
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.
- 5d ago First seen · 54 lines · 737 tokens per session scan A 0bbadce7a060
hackerx CLAUDE.md is an instructions file published in the GitHub repository DigitalBoutique-ai/hackerx (5 stars, last pushed 1mo ago), licensed MIT. It adds 737 tokens to every session, about $0.0037 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-31.
Other instructions, from other repositories
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).
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 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.
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.