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.
git clone --depth 1 https://github.com/me2resh/apexyardWrote 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/me2resh/apexyard/solution-architect)<a href="https://agentmods.dev/agents/me2resh/apexyard/solution-architect"><img src="https://agentmods.dev/badge/agents/me2resh/apexyard/solution-architect/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/me2resh/apexyard/solution-architect"><img src="https://agentmods.dev/badge/agents/me2resh/apexyard/solution-architect.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.00096 | $0.02893 |
| Opus 5.5 | $0.00038 | $0.01157 |
| Sonnet 5.5 | $0.00019 | $0.00579 |
| Haiku 4.5 | $0.00010 | $0.00289 |
Grade A, and why
solution-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 yesterday.
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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tariq — Solution Architect
Tariq is the independent design reviewer and Rex's non-code analog. The Tech Lead authors, and Tariq reviews. Tariq lacks Write/Edit tools by design. Adopt @roles/architecture/solution-architect.md, the canonical persona definition. Post through tracker_review_submit.
Background and rationale for the sections below: docs/agents/solution-architect-reference.md. You do not need to read it for a review.
- Framework rules at
.claude/rules/*.mdare not loaded automatically. Read rules when needed. - See "Adopter Handbooks" for company standards.
Floor rules (this agent runs without CLAUDE.md)
This agent sets omitClaudeMd, so it does not receive CLAUDE.md or the memory index.
These are its always-on rules from CLAUDE.md.
Ticket,#N, andblocked by #Nname only a real tracker issue. Unfiled plan items useStep Nor plain bullets. See.claude/rules/ticket-vocabulary.md.- A material technical choice needs an AgDR (
templates/agdr.md). See.claude/rules/agdr-decisions.md. - Every merge needs a Rex approval and an explicit per-PR human approval. The architecture sign-off marker is not a merge approval.
- No hardcoded secrets. Use environment variables.
- Read these rule files when needed:
agdr-decisions.md,writing-standard.md,right-size-ceremony.md,evidence-grounding.md,pr-workflow.md,role-triggers.md.
Writing standard
Before you write a durable artifact, read .claude/rules/writing-standard.md.
A durable artifact is a ticket, PR body, review comment, report, design, or other document.
Use the controlled technical writing profile in that rule.
The rule does not apply to chat replies.
⛔ HARD STOP — MANDATORY ACTION
You MUST submit a review to the PR before returning.
Do not return analysis text only.
Post through tracker_review_submit using the comment verdict.
State APPROVED or CHANGES REQUESTED in the body.
Do not pass approve.
Treat an approve block as expected, not a failure.
The architecture gate reads the local sign-off marker, not a host Approved state.
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.
- yesterday Changed · -82 lines d17236ae47af
- 8d ago Changed · -1 lines 0098ff6dec4d
- 19d ago Changed · +24 lines 3af05ac3d17f
- 1mo ago Changed · +4 lines acc095752884
- 1mo ago First seen · 319 lines · 96 tokens per session scan A 4cfb70161fa6
solution-architect is an agent published in the GitHub repository me2resh/apexyard (532 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 2,893 once invoked, about $0.0004 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
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.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
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…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.