Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Hainrixz/the-architect/plugin install 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/commands/hainrixz/the-architect/architect)<a href="https://agentmods.dev/commands/hainrixz/the-architect/architect"><img src="https://agentmods.dev/badge/commands/hainrixz/the-architect/architect/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/commands/hainrixz/the-architect/architect"><img src="https://agentmods.dev/badge/commands/hainrixz/the-architect/architect.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.00049 | $0.01327 |
| Opus 5.5 | $0.00020 | $0.00531 |
| Sonnet 5.5 | $0.00010 | $0.00265 |
| Haiku 4.5 | $0.00005 | $0.00133 |
Grade A, and why
architect 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect — design a new project end to end
You are being invoked as the /architect slash command. This file sets the mode. It does not
contain the interview — the interview lives in questions/ and is the single source of truth.
Read these before saying anything to the user:
- Plugin install:
${CLAUDE_PLUGIN_ROOT}/skills/architect/SKILL.md - Clone install:
./CLAUDE.mdat the repo root — the clone-mode mirror of the skill. Same rules, same state machine, repo-relative paths, and the subagent work done inline.
Read the skill end to end, then execute the four phases exactly as written there.
Mode
| Setting | Value |
|---|---|
| Entry | Greenfield — nothing exists yet |
| Depth | Full 4-phase interview |
| Question budget | Max 3 per message, conversational |
| Output | Bundle or single file — derived and announced at phase-4 Step 2 (12 or more steps = bundle); an explicit user preference wins. Both land in the user's cwd under ./blueprints/: ./blueprints/<project-slug>/ for a bundle, ./blueprints/<project-slug>-blueprint.md for a single file. |
| Gate | blueprint-validator must return PASS before you hand anything over |
${CLAUDE_PLUGIN_ROOT}/questions/phase-4-generate.md Step 3 is the authority on the emitted tree —
do not reproduce it from memory here. One thing worth repeating: .claude/commands/ is never
emitted into a generated project. A slash command only fires when a human types it, and an
autonomous builder types nothing; repeatable project workflows go in .claude/skills/<name>/SKILL.md.
Phase pointers — read, never paraphrase from memory
| Phase | Read | Produces |
|---|---|---|
| 1 · Discovery | ${CLAUDE_PLUGIN_ROOT}/questions/phase-1-discovery.md |
The shape → ${CLAUDE_PLUGIN_ROOT}/knowledge/shapes/<shape>.md |
| 2 · Deep dive | ${CLAUDE_PLUGIN_ROOT}/questions/phase-2-branches.md |
Runtime track + capability set |
| 3 · Architecture | ${CLAUDE_PLUGIN_ROOT}/questions/phase-3-confirmation.md |
Confirmed stack, signed off by the user |
| 4 · Generate | ${CLAUDE_PLUGIN_ROOT}/questions/phase-4-generate.md |
The bundle, then the validator |
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 Changed · +2 lines acadbb1020aa
- 1mo ago First seen · 101 lines · 49 tokens per session scan A c931136c4d28
architect is a command published in the GitHub repository Hainrixz/the-architect (561 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 1,327 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-08-30.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
discuss
A command that interviews you in five phases and saves a detailed description of a proposed feature or change. EARS is a structured way to write requirements so they can be checked clearly.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
rev
Invoke Code Reviewer for code quality, security, requirements validation, and best practices review.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.