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-audit)<a href="https://agentmods.dev/commands/hainrixz/the-architect/architect-audit"><img src="https://agentmods.dev/badge/commands/hainrixz/the-architect/architect-audit/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-audit"><img src="https://agentmods.dev/badge/commands/hainrixz/the-architect/architect-audit.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.00065 | $0.01139 |
| Opus 5.5 | $0.00026 | $0.00456 |
| Sonnet 5.5 | $0.00013 | $0.00228 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
architect-audit 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect-audit — validate an existing blueprint
You are being invoked as /architect-audit. This command is read-only. It grades a blueprint;
it does not rewrite one.
Say this before you dispatch anything, whenever the target has no tasks.json beside it: a
blueprint written before v2 will FAIL, with a long finding list. It has no acceptance criteria at
all — that is the single thing the validator measures most of — plus no tasks.json, no epics, and
no verify commands. The failure is a diagnosis of a format gap, not evidence that the tool is broken
or that the design is bad. Setting that expectation up front is part of the job, because a
twenty-finding report delivered without it reads as an accusation.
The rubric lives in the validator, not here:
${CLAUDE_PLUGIN_ROOT}/agents/blueprint-validator.md. Read it before reporting, so your summary
uses the validator's own check names instead of invented ones.
Resolve the target
$ARGUMENTS is a path. Handle these cases:
| Argument | Do |
|---|---|
A .md file |
Audit that file. |
| A directory | Glob it for the canonical bundle tree — blueprint.md, tasks.json, epics/*.md, and workspace/ (workspace/CLAUDE.md, workspace/AGENTS.md, workspace/.claude/). Audit the bundle as a whole — a bundle missing tasks.json is itself a finding, and so is a workspace/.claude/commands/ directory, which is never emitted. |
| Empty | Glob ./blueprints/*/ in the cwd, then ./blueprints/*-blueprint.md for single-file mode. One match → use it. Several → list them and ask which. None → say so and point at /architect. |
| A path that does not exist | Say so. Do not guess a neighbor. |
Run
Dispatch blueprint-validator with the Agent tool (formerly Task), handing it the resolved path. Do
not grade the blueprint yourself while the subagent is available — a second opinion from the same
context is not a second opinion. If dispatch fails, run the sweeps from
${CLAUDE_PLUGIN_ROOT}/agents/blueprint-validator.md in the main thread, say so in one line, and label
the verdict self-audited — see Never hard-depend on a subagent in
${CLAUDE_PLUGIN_ROOT}/questions/phase-4-generate.md.
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 · +7 lines e57cbc96b6eb
- 1mo ago First seen · 79 lines · 65 tokens per session scan A b3ea6b29815d
architect-audit is a command published in the GitHub repository Hainrixz/the-architect (561 stars, last pushed 5d ago), licensed MIT. It adds 65 tokens to every session and 1,139 once invoked, about $0.0003 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.