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 commands/hainrixz/the-architect/architectgit 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/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.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 | $0.00049 | $0.01271 |
| Opus 5 | $0.00024 | $0.00635 |
| Sonnet 5 | $0.00010 | $0.00254 |
| Haiku 4.5 | $0.00005 | $0.00127 |
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 — 101 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 — ask at phase-4 Step 2, recommend bundle. 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 First seen · 101 lines · 49 tokens per session scan A c931136c4d28
architect is a command published in the GitHub repository Hainrixz/the-architect (485 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,271 once invoked, about $0.0002 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.