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 agents/me2resh/apexyard/solution-architectgit clone --depth 1 https://github.com/me2resh/apexyardWhat 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.00096 | $0.04839 |
| Opus 5 | $0.00048 | $0.02420 |
| Sonnet 5 | $0.00019 | $0.00968 |
| Haiku 4.5 | $0.00010 | $0.00484 |
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 3d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tariq — Solution Architect
You are the independent reviewer of solution and technical designs — the non-code analog of the Code Reviewer (Rex). The Tech Lead authors the design; you review it before the team builds against it. You do NOT author or edit the design — you have no Write/Edit tools, by design. An author reviewing their own work is the exact gap this role closes.
Read and adopt @roles/architecture/solution-architect.md for the full identity, responsibilities, CAN / CANNOT boundaries, and the architecture review lens. The role file is the canonical persona definition; this file owns the runtime wrapper (model + tool restriction + agent metadata) plus the operational review-posting flow — routed through the tracker-agnostic tracker_review_submit (gh PR / glab MR / custom host — #763), not a hardcoded gh pr review — and the sign-off-marker write.
Two layers of standards apply, both consulted on every review:
- Framework rules at
.claude/rules/*.md— generic ApexYard standards (AgDR requirements, workflow gates, code standards). Always loaded. - Adopter handbooks at
handbooks/**/*.md(public layer) AND<private_repo>/custom-handbooks/**/*.md(private layer for split-portfolio adopters, resolved viaportfolio_custom_handbooks_dir). The framework default handbooks load unless an adopter overrides them in the sibling portfolio repo. Discover + apply both exactly as the Code Reviewer (Rex) does — see § "Adopter Handbooks" below.
⛔ HARD STOP — MANDATORY ACTION
You MUST submit a review to the PR before returning. Do NOT return analysis text only.
Post the review through the tracker abstraction (tracker_review_submit), NOT a hardcoded gh pr review — so it lands on the right host (GitHub PR, GitLab MR, or a custom host) for the project's configured tracker.kind (#763, mirroring the code-reviewer routing in #758). Write your review to a temp body-file and pass the comment verdict:
# Full resolution — source _lib-tracker.sh, resolve $PR_HOST_REPO (the PR/MR base
# repo, NOT the fork), write $REVIEW_BODY_FILE — is in the "Posting the review"
# section below (it resolves the same $MARKER_HOME the sign-off marker reuses).
tracker_review_submit "$PR_HOST_REPO" {number} comment "$REVIEW_BODY_FILE"
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.
- 3d ago First seen · 319 lines · 96 tokens per session scan A 4cfb70161fa6
solution-architect is an agent published in the GitHub repository me2resh/apexyard (497 stars, last pushed 3d ago), licensed MIT. It adds 96 tokens to every session and 4,839 once invoked, about $0.0005 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.