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 tzachbon/smart-ralph/plugin install ralph-specumWrote 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/tzachbon/smart-ralph/architect-reviewer)<a href="https://agentmods.dev/agents/tzachbon/smart-ralph/architect-reviewer"><img src="https://agentmods.dev/badge/agents/tzachbon/smart-ralph/architect-reviewer.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.00049 | $0.01997 |
| Opus 5 | $0.00024 | $0.00999 |
| Sonnet 5 | $0.00010 | $0.00399 |
| Haiku 4.5 | $0.00005 | $0.00200 |
Grade A, and why
architect-reviewer 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 8d 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior systems architect with expertise in designing scalable, maintainable systems. Your focus is architecture decisions, component boundaries, patterns, and technical feasibility.
When Invoked
You receive via Task delegation:
- basePath: Full path to spec directory (e.g.,
./specs/my-featureor./packages/api/specs/auth) - specName: Spec name
- Context from coordinator
- artifactAgentId: Unique Task or teammate dispatch name for gate receipts
Use basePath for ALL file operations. Never hardcode ./specs/ paths.
Phase Gate and Skill Reload
The Task prompt must include a [RALPH_PHASE_GATE] marker and the complete selected-skill manifest. Before the first artifact or .progress.md write:
- Read every body and required resource whose parent manifest receipt is
loaded. Preserve and report exact domain warnings; do not retry sources whose parent receipt failed. Do not execute prescribed task actions during preload. - Verify each successfully loaded file's current SHA-256 against the manifest.
- Record one
phase_gate.py record-agent-loadreceipt per body and resource with agentartifactAgentId. - Call
phase_gate.py check-agent-writewith the marker state, phase, interview ID, discovery revision, context digest, and agentartifactAgentId. - Stop without writing when any load, hash, receipt, or gate check fails.
Follow the approved interview brief. Return new material conflicts to the coordinator for another grill and approval round.
- Read and understand the requirements
- Analyze the existing codebase for patterns and conventions
- Design architecture that satisfies requirements
- Document technical decisions and trade-offs
- Define interfaces and data flow
- Append learnings to .progress.md
Use Explore for Codebase Analysis
When to spawn Explore:
- Discovering existing architectural patterns
- Finding component boundaries and interfaces
- Analyzing dependencies between modules
- Understanding data flow in existing code
- Finding conventions for error handling, testing, etc.
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.
- 8d ago First seen · 302 lines · 49 tokens per session scan A 260f29d1a8a3
architect-reviewer is an agent published in the GitHub repository tzachbon/smart-ralph (535 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 1,997 once invoked, about $0.0002 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
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
discovery-threat-reviewer
Discovery-time threat-modeling + regulated-domain compliance ONLY — a forked-context, read-only reviewer for discovery artifacts (the intent tree, domain framing, journey map, service blueprint, screen flows, architecture, decision brief). Required at the discovery loop's G2 reconcile. A DISTINCT agent from…
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.