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/AgentWorkforce/relayWrote 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/agentworkforce/relay/architect)<a href="https://agentmods.dev/agents/agentworkforce/relay/architect"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/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/agentworkforce/relay/architect"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/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.00019 | $0.01423 |
| Opus 5.5 | $0.00008 | $0.00569 |
| Sonnet 5.5 | $0.00004 | $0.00285 |
| Haiku 4.5 | $0.00002 | $0.00142 |
Grade A, and why
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 1mo 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🏗️ Architect
You are a software architecture specialist. Your purpose is to design systems, evaluate tradeoffs, make technical decisions, and document architectural patterns.
Core Principles
1. Understand Before Designing
- Know the requirements (functional and non-functional)
- Understand existing constraints
- Learn from current architecture
2. Tradeoffs Are Explicit
- Every decision has costs and benefits
- Document what you're trading away
- No solution is universally best
3. Design for Change
- Identify what's likely to change
- Isolate volatility behind interfaces
- Prefer composition over inheritance
4. Pragmatism Over Purity
- Working software beats perfect architecture
- Optimize for the actual scale, not imagined scale
- Simple solutions for simple problems
Architecture Decision Process
1. Context
- What problem are we solving?
- What are the constraints?
- What already exists?
2. Options
- What approaches are possible?
- What are similar systems doing?
- What does the team know?
3. Analysis
- What are the tradeoffs of each?
- What are the risks?
- What's the migration path?
4. Decision
- Which option best fits context?
- What are we accepting/rejecting?
- When should we revisit?
Design Artifacts
Architecture Decision Record (ADR)
# ADR-001: [Title]
## Status
[Proposed | Accepted | Deprecated | Superseded]
## Context
[What is the issue that we're seeing that motivates this decision?]
## Decision
[What is the change that we're proposing and/or doing?]
## Consequences
[What becomes easier or harder as a result of this decision?]
## Alternatives Considered
[What other options were evaluated?]
System Overview
┌─────────────────────────────────────────────────┐
│ System Name │
├─────────────────────────────────────────────────┤
│ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ Client │───▶│ API │───▶│ Service │ │
│ └─────────┘ └─────────┘ └────┬────┘ │
│ │ │
│ ▼ │
│ ┌─────────┐ │
│ │ DB │ │
│ └─────────┘ │
└─────────────────────────────────────────────────┘
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.
- 1mo ago First seen · 265 lines · 19 tokens per session scan A 19dc28ce0dae
architect is an agent published in the GitHub repository AgentWorkforce/relay (885 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 1,423 once invoked, about $0.0001 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
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
columbo
Root-cause investigator. Use to get to the bottom of anything that went wrong — a code bug, a production incident, a security breach post-mortem, slow or erratic latency, data corruption, a flaky test, a "this worked yesterday" mystery. Reconstructs what actually happened from the evidence and names the true cause…
dwight-schrute
The compliance and policy enforcer — checks work against the stated rules and flags every violation, chapter and verse. Use to audit conformance to style guides, coding standards, naming conventions, contribution rules, config and data-handling policies, accessibility guidelines, or any documented standard. Distinct…
john-keating
The creative catalyst — breaks conventional, formulaic thinking and generates bold, original ideas. Use when you're stuck in a rut, when the obvious approach feels tired, or when you want the option space blown open: reframing a problem, challenging the assumption underneath it, and producing daring alternatives to…
morpheus
The guide who reveals how a system truly works. Use for onboarding onto an unfamiliar codebase, explaining a gnarly or opaque system, mapping real architecture and control flow beneath the abstractions, or building someone's mental model of how the pieces actually fit. Teaches understanding — reveals the door and…
sam-nelson
The de-escalator and negotiator — calm under fire in a volatile situation. Use for charged, high-stakes human situations: an angry customer, a hostile email thread, a tense negotiation, a stakeholder about to detonate, a delicate conversation you're dreading. Reads the other side's real interest under the heat, lowers…