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/architect-quickgit 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-quick)<a href="https://agentmods.dev/commands/hainrixz/the-architect/architect-quick"><img src="https://agentmods.dev/badge/commands/hainrixz/the-architect/architect-quick.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.00043 | $0.01329 |
| Opus 5 | $0.00022 | $0.00665 |
| Sonnet 5 | $0.00009 | $0.00266 |
| Haiku 4.5 | $0.00004 | $0.00133 |
Grade A, and why
architect-quick 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect-quick — fast-track
You are being invoked as /architect-quick. Same machinery as /architect, compressed interview.
Read the skill first — it is still the source of truth:
- 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.
Mode
| Setting | Value |
|---|---|
| Entry | Greenfield |
| Depth | 3 questions, one message, then defaults |
| Output | Recommend single file — quick mode implies a small build — and confirm it, because ${CLAUDE_PLUGIN_ROOT}/questions/phase-4-generate.md Step 2 is authoritative on emission mode. This row is input to your recommendation, not the decision. Fold the confirmation into the architecture card in Flow step 3 so it costs no extra round. Confirmed single file → ./blueprints/<project-slug>-blueprint.md in the user's cwd; bundle → ./blueprints/<project-slug>/. |
| Gate | blueprint-validator must return PASS — speed does not buy an exemption |
The three questions — ask all three in ONE message
- What is it? One or two sentences.
- Who uses it? Public users, an internal team, other developers — and roughly how many.
- Any tech you must use or must avoid? Existing stack, hosting constraint, language. "No preference" is a valid answer and the fastest one.
If $ARGUMENTS already answers Q1, say so and ask only Q2 and Q3. Do not re-ask what you were told.
Then stop asking. Everything else is a default you choose and state out loud.
Defaults — decide, announce, do not ask
| Decision | Default |
|---|---|
| Shape | Classify from the three answers using ${CLAUDE_PLUGIN_ROOT}/questions/phase-1-discovery.md. Ambiguous → pick the closer one and say which and why. |
| Runtime track | The shape file's Default runtime track. Deviate only if Q3 forces it. |
| Capabilities | The shape file's Core capabilities table, nothing extra. |
| Pins | From the stack-researcher report produced in this session — it is authoritative. ${CLAUDE_PLUGIN_ROOT}/knowledge/runtime-tracks/<track>.md is the fallback for any package the researcher did not resolve, and its unverified caveats carry through verbatim. Never write a pin from memory. |
| Stage | MVP. Testing is smoke-level, observability is logs plus error tracking. |
| Scope | The shape's build order, trimmed to what ships something usable. |
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 · 96 lines · 43 tokens per session scan A 2c89469c6f7c
architect-quick is a command published in the GitHub repository Hainrixz/the-architect (485 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,329 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.