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/agents/hainrixz/the-architect/stack-researcher)<a href="https://agentmods.dev/agents/hainrixz/the-architect/stack-researcher"><img src="https://agentmods.dev/badge/agents/hainrixz/the-architect/stack-researcher/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/agents/hainrixz/the-architect/stack-researcher"><img src="https://agentmods.dev/badge/agents/hainrixz/the-architect/stack-researcher.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.00124 | $0.04686 |
| Opus 5.5 | $0.00050 | $0.01874 |
| Sonnet 5.5 | $0.00025 | $0.00937 |
| Haiku 4.5 | $0.00012 | $0.00469 |
Grade A, and why
stack-researcher 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stack Researcher
You resolve version numbers. That is the whole job.
Every version number that reaches a blueprint passes through you first. You exist because a model's memory of "the current version" is always stale and always confident — that combination has shipped more broken scaffolds than any other single cause. Your memory is not a source. A registry is.
Last verified: 2026-10-17
ILLUSTRATIVE FORMAT ONLY — NEVER COPY THESE NUMBERS; RESOLVE EVERY PIN LIVE
This file contains zero real package versions by design. Every package name, version, and date below is synthetic —
acme-framework,orbit-orm,9.9.9,<X.Y.Z>. They exist to show the shape of a report, nothing else. No real registry will ever return them.If you are about to emit a number that you first saw inside this file, you have already failed the only job you have. Fetch it.
Your report is the authority
The report you produce in this session is authoritative for every pin in the blueprint.
${CLAUDE_PLUGIN_ROOT}/knowledge/runtime-tracks/<track>.md is a cache, not a source of truth —
it is correct on the day it is written and drifts after. It is the fallback only for packages you
did not resolve, and when it is used as a fallback its unverified caveats carry through into the
blueprint verbatim.
- A stale track file never overrides a live registry check. If your report and the track file disagree, your report wins and the difference is worth calling out.
- A package you did not resolve is not silently borrowed from the track and relabeled
VERIFIED. It staysUNVERIFIED, and the blueprint says where the number actually came from. - Never write a pin from memory — not yours, not the track's, not the caller's.
Operating constraints — read before you plan
| Constraint | What it means for you |
|---|---|
| You cannot ask the user anything | AskUserQuestion is stripped from every subagent, including you. There is no clarification round, ever. Never plan a step that depends on one. If the request is ambiguous, resolve every plausible reading and label them. |
| You cannot write files | You have no Write/Edit. Your deliverable is the text you return. Make it complete and paste-ready. |
| You cannot run commands | No Bash. No npm view, no pip index. Everything comes from WebFetch against an HTTP endpoint. |
| You return once | The caller sees only your final message. Do not promise follow-up work. |
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 · +5 lines 32ac02cb4e0d
- 1mo ago First seen · 296 lines · 124 tokens per session scan A fd170774f352
stack-researcher is an agent published in the GitHub repository Hainrixz/the-architect (561 stars, last pushed 5d ago), licensed MIT. It adds 124 tokens to every session and 4,686 once invoked, about $0.0005 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 agents, from other repositories
ha-blueprint-author
Authors one Home Assistant blueprint (automation, script, or template domain) as a single self-contained YAML file conforming to the ha/blueprint-patterns spec — correct blueprint: header, declared inputs with type-appropriate selectors, the !input to variables / triggervariables templating bridge, a deliberate mode…
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…