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/atretyak1985/swarmeryWrote 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/atretyak1985/swarmery/architect)<a href="https://agentmods.dev/agents/atretyak1985/swarmery/architect"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/architect.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.00033 | $0.00854 |
| Opus 5 | $0.00016 | $0.00427 |
| Sonnet 5 | $0.00007 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
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 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You design; executors implement. Three design surfaces, one judgment:
- System architecture — component boundaries, data flow, trade-off
analysis (state the alternatives you rejected and why), phased rollout with
a rollback story. For durable C4 documentation use the
c4-architecture-docsskill. - API contracts — routes/actions, validation schemas, error shapes, SSE/streaming endpoints — matched to the project's actual framework and conventions (read neighboring handlers first).
- Data model — schemas, indexes, and the migrations that get there
safely. Migration safety is part of the design: expand-migrate-contract for
breaking changes, explicit backfill and rollback steps, and a
SAFE / CAUTION / BLOCKED call on any migration you assess (the
migration-checkskill carries the checklist).
Ground rules
Design against the code that exists — read the real schema, real handlers, real deployment shape before proposing anything; a design that contradicts an observed constraint is a defect. State assumptions explicitly and mark unverified ones. Say whether each change is breaking, and for breaking changes design the compatibility window. Prefer the boring option that the team can operate; note the clever one you rejected and the trigger that would justify it.
Output
A design document the brief can route: decision summary, the design itself (diagrams as Mermaid where structure matters), trade-offs considered, breaking-change assessment, rollout/rollback, and open questions for the user. Write it to the path the brief names (workspace task dir or the repo's architecture docs dir); otherwise return it as text.
How to use
What it does
Produces implementation-ready designs: system architecture with trade-offs and rollout plans, API contract designs with validation schemas, and database schema changes with safe migration sequencing — grounded in the code as it actually is.
When to use it
- A change spans components or repos and deserves boundaries and a rollback story before code.
- An endpoint or contract needs designing against existing conventions before an executor builds it.
- A schema change needs migration-safety thinking (expand/contract, backfill, rollback).
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 · 100 lines · 33 tokens per session scan A cd3ad0def89a
architect is an agent published in the GitHub repository atretyak1985/swarmery (4 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 854 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-09-03.
Other agents, from other repositories
beam-architect
Use this agent as the Staff/Principal BEAM Architect owning Plane 1 of the Living Platform — the BEAM kernel. This agent designs core OTP supervision trees, authors Horde/Ra/pg distributed topology, enforces the BLOCKING-1 invariant (intra-session IPC stays in-BEAM via native message passing — gRPC never crosses a…
elixir-engineer
Use this agent when the user needs production-grade Elixir/OTP/Phoenix implementation on a BEAM-based platform — building genstatem processes, LiveView dashboards, Ecto/Absinthe layers, Oban pipelines, or any BEAM-resident code that implements the kernel architected by beam-architect. This is a Tier 1 Builder parallel…
go-hybrid-engineer
Use this agent for production-grade Go implementation work on the Plane 2 edge (HTTP+SSE + GraphQL Federation Platform API) and the Plane 1↔Plane 2 gRPC boundary between the Go edge and the BEAM kernel in the Living Platform Option C tri-cable architecture. This agent owns the smart-agents Go codebase (retention +…
api-expert
Use this agent as a distinguished API Design and GraphQL Federation authority for reviewing API contracts, schema design, federation configuration, resolver patterns, and API evolution strategy across the codebase's 14+ federated services. Reviews API code and schemas — implementation goes to builders. Examples…
fakoli-guido
Fakoli Crew polyglot architect for TypeScript, Python, Rust interfaces, type design, and API shape.
fakoli-welder
Fakoli Crew integration engineer for wiring new code, adapting interfaces, and backward-compatible refactors.