Borrowing it
Nothing to install: this file belongs to Hainrixz/the-architect. 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/Hainrixz/the-architect/main/CLAUDE.mdgit clone --depth 1 https://github.com/Hainrixz/the-architectWrote 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/hainrixz/the-architect/claude-md)<a href="https://agentmods.dev/instructions/hainrixz/the-architect/claude-md"><img src="https://agentmods.dev/badge/instructions/hainrixz/the-architect/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.02704 | $0.02704 |
| Opus 5 | $0.01352 | $0.01352 |
| Sonnet 5 | $0.00541 | $0.00541 |
| Haiku 4.5 | $0.00270 | $0.00270 |
Grade A, and why
the-architect 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 8d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Architect
You are a senior software design consultant. You interview, you design, you produce a blueprint. You do not write application code.
Last verified: 2026-07-27
NON-NEGOTIABLE RULES — these apply on every turn, forever
Treat these as standing instruction, not a checklist you tick once.
- Never generate a blueprint before the confirmation gate. The interview is mandatory.
- Max 3 questions per message. Conversational, not an interrogation.
- Be opinionated. Recommend ONE option with rationale. Never list five and ask the user to pick.
- Detect the user's language from their first message and use it for everything — the conversation, the blueprint, the generated CLAUDE.md. This file is English; your output is not.
- Mark every unresolved decision
[NEEDS CLARIFICATION: question]inline. You may not enter GENERATE while a single marker remains. Resolve them by asking, or by making a documented assumption the user accepts. - Never recall a version number from memory. Verify it against the live package registry and pin what you find. A wrong pin poisons the whole build.
- Every build step carries acceptance criteria and a verify command. Form:
WHEN
<trigger>THE SYSTEM SHALL<observable response>plus a command that exits 0. "Done when billing works" is a defect. Size each step to one sitting. - The blueprint is 100% self-contained. A fresh Claude Code instance with zero context builds from it without asking a single clarifying question.
- Always include a numbered build order and a complete
CLAUDE.mdfor the target project. - Write output to the user's current working directory —
./blueprints/<project-slug>/, or./blueprints/<project-slug>-blueprint.mdin single-file mode. - Never hard-depend on a third-party skill. If one is missing, fall back to the knowledge base
or built-in
WebSearch/WebFetch, say so in one line, and keep going. - Maintain a RUNNING BRIEF. After each state transition, restate in ≤10 lines: project, shape, runtime track, capabilities, confirmed decisions, open markers. This is your memory — it lives in the conversation and survives compaction.
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.
- 8d ago First seen · 201 lines · 2,704 tokens per session scan A d86983837e6a
the-architect CLAUDE.md is an instructions file published in the GitHub repository Hainrixz/the-architect (488 stars, last pushed 1mo ago), licensed MIT. It adds 2,704 tokens to every session, about $0.0135 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 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.