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-refreshgit 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-refresh)<a href="https://agentmods.dev/commands/hainrixz/the-architect/architect-refresh"><img src="https://agentmods.dev/badge/commands/hainrixz/the-architect/architect-refresh.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.00062 | $0.01263 |
| Opus 5 | $0.00031 | $0.00632 |
| Sonnet 5 | $0.00012 | $0.00253 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
architect-refresh 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 6d 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-refresh — un-rot a blueprint
You are being invoked as /architect-refresh. A blueprint written months ago is still
architecturally sound and numerically wrong. This command fixes the numbers and flags the migrations
they imply. It does not re-open the design.
The research contract lives in ${CLAUDE_PLUGIN_ROOT}/agents/stack-researcher.md. Read it first.
Resolve the target
$ARGUMENTS is a path, optionally followed by --apply.
| Argument | Do |
|---|---|
A .md file |
Refresh that file. |
| A directory | Refresh blueprint.md, plus any pins that leaked into workspace/CLAUDE.md, workspace/.claude/** or epics/*.md. |
| Empty | Glob ./blueprints/*/, then ./blueprints/*-blueprint.md for single-file mode. One match → use it. Several → ask. None → say so. |
--apply present |
Skip the confirmation step in Phase 3 below and edit directly. |
Phase 1 — extract
Grep the blueprint for every pinned version: the tech stack table, setup commands, lockfile snippets, Dockerfile base images, CI runner versions, runtime/SDK minimums. Build the inventory:
Layer | Package or runtime | Pinned in blueprint | Where it appears (section + line)
Services without versions — Stripe, Supabase, Cloudflare and friends — are not pins. Skip them unless the blueprint names a specific API version.
Phase 2 — verify
Dispatch stack-researcher once, with the whole inventory. One batched subagent, not one per
package. It resolves each package against its live registry and returns current stable, whether the
gap crosses a major, and any rename or removal in between.
Never answer from memory. A pin you recall is a pin you are about to get wrong.
Phase 3 — the drift report
Print one table:
Layer | Pinned | Current | Gap | Breaking? | Action | Risk
- Gap — patch, minor, major, or
unverifiedif the registry could not be reached. Sayunverifiedout loud; a confident guess is worse than an honest gap. - Breaking? — yes only when the changelog says so. Cite what changed: a rename, a removed flag, a raised runtime floor.
- Action —
bump,bump + migrate,hold(with the reason), orreplace(package is dead). - Risk — what breaks in this blueprint if the bump lands, in one clause.
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.
- 6d ago First seen · 103 lines · 62 tokens per session scan A 6312a97b6486
architect-refresh is a command published in the GitHub repository Hainrixz/the-architect (485 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 1,263 once invoked, about $0.0003 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.