Borrowing it
Nothing to install: this file belongs to GabrielAmz/web-anatomy. 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/GabrielAmz/web-anatomy/main/CLAUDE.mdgit clone --depth 1 https://github.com/GabrielAmz/web-anatomyWrote 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/gabrielamz/web-anatomy/claude-md)<a href="https://agentmods.dev/instructions/gabrielamz/web-anatomy/claude-md"><img src="https://agentmods.dev/badge/instructions/gabrielamz/web-anatomy/claude-md/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/instructions/gabrielamz/web-anatomy/claude-md"><img src="https://agentmods.dev/badge/instructions/gabrielamz/web-anatomy/claude-md.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.00517 | $0.00517 |
| Opus 5 | $0.00259 | $0.00259 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
web-anatomy 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 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Web Anatomy
Claude Code-specific notes. The full cross-agent install instructions are in AGENTS.md.
Slash command shortcuts
After install, every skill is available as a slash command in Claude Code:
/webanatomy-setup
/find-examples
/audit-page
/research-best-practices
/write-page
/build-page
First-run order
- Run
/webanatomy-setuponce to capture product, ICP, industry, competitors, proof assets, and priority pages. This writes.agents/webanatomy-context.md. - Then run the benchmark-backed workflows:
/find-examples(market view),/audit-page(diagnose your page),/research-best-practices(tiered ladder for one section),/write-page(the grounded rework or a new build), or/build-page(assemble structure + copy into a shareable wireframe).
The two flows
Both end in a shareable wireframe:
- Improve:
/audit-page→/write-page→/build-page(optional, in your page's own look). - Create:
/find-examples(pick one exemplar) →/write-pagebuild mode (light outline adopts the exemplar's section order, then writes copy) →/build-page(assemble in the exemplar's look).
write-page is the copy engine; build-page is the terminal assembler. The single chosen exemplar drives both structure and design.
Visual Output
The benchmark workflows write visual reports under .webanatomy/ with report.md, report.html, and a references/ folder for screenshots. Prefer opening the HTML report for visual review; chat summaries should stay short.
Skill discovery
Claude reads the description: field from each SKILL.md front matter when deciding which skill to activate. Web Anatomy descriptions are deliberately verbose (200-400 words) and pack in trigger phrases like "build me a landing page," "create a homepage," "this page isn't converting." That's intentional — the description IS the routing layer.
If the wrong skill activates, paste the slug explicitly: Use /write-page to audit this pricing page....
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 · 55 lines · 517 tokens per session scan A 3877b3fb2041
web-anatomy CLAUDE.md is an instructions file published in the GitHub repository GabrielAmz/web-anatomy (8 stars, last pushed 2mo ago), licensed MIT. It adds 517 tokens to every session, about $0.0026 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
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.
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).
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).
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.
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.