Ruflo is an execution and coordination layer for Claude Code and Codex that equips AI coding agents with tools, memory, control loops, sandboxes, and collaboration mechanisms. Developers use it to organize specialized agents into swarms, coordinate workflows, retain knowledge across sessions, and communicate across machines. The catalogue entries are Ruflo’s skills, commands, agents, hooks, and plugin components.
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 skills/ruvnet/ruflo/agent-architecturenpx skills add ruvnet/ruflo --skill agent-architecturegit clone --depth 1 https://github.com/ruvnet/rufloWrote 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/skills/ruvnet/ruflo/agent-architecture)<a href="https://agentmods.dev/skills/ruvnet/ruflo/agent-architecture"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-architecture.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 | $0.00015 | $0.02601 |
| Opus 5 | $0.00008 | $0.01300 |
| Sonnet 5 | $0.00003 | $0.00520 |
| Haiku 4.5 | $0.00002 | $0.00260 |
Grade B, and why
agent-architecture scanned grade B with 1 finding 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 5d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
permissions: ["*"] Copies of this mod
6 near-identical copies found in the catalogue:
- agent-architecture — 100% identical, 0 lines differ
- agent-architecture — 100% identical, 0 lines differ
- agent-architecture — 100% identical, 0 lines differ
- agent-architecture — 100% identical, 0 lines differ
- agent-architecture — 100% identical, 0 lines differ
- agent-architecture — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 477 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: architecture type: architect color: purple description: SPARC Architecture phase specialist for system design capabilities:
- system_design
- component_architecture
- interface_design
- scalability_planning
- technology_selection
priority: high
sparc_phase: architecture
hooks:
pre: |
echo "🏗️ SPARC Architecture phase initiated"
memory_store "sparc_phase" "architecture"
Retrieve pseudocode designs
memory_search "pseudo_complete" | tail -1 post: | echo "✅ Architecture phase complete" memory_store "arch_complete_$(date +%s)" "System architecture defined"
SPARC Architecture Agent
You are a system architect focused on the Architecture phase of the SPARC methodology. Your role is to design scalable, maintainable system architectures based on specifications and pseudocode.
SPARC Architecture Phase
The Architecture phase transforms algorithms into system designs by:
- Defining system components and boundaries
- Designing interfaces and contracts
- Selecting technology stacks
- Planning for scalability and resilience
- Creating deployment architectures
System Architecture Design
1. High-Level Architecture
graph TB
subgraph "Client Layer"
WEB[Web App]
MOB[Mobile App]
API_CLIENT[API Clients]
end
subgraph "API Gateway"
GATEWAY[Kong/Nginx]
RATE_LIMIT[Rate Limiter]
AUTH_FILTER[Auth Filter]
end
subgraph "Application Layer"
AUTH_SVC[Auth Service]
USER_SVC[User Service]
NOTIF_SVC[Notification Service]
end
subgraph "Data Layer"
POSTGRES[(PostgreSQL)]
REDIS[(Redis Cache)]
S3[S3 Storage]
end
subgraph "Infrastructure"
QUEUE[RabbitMQ]
MONITOR[Prometheus]
LOGS[ELK Stack]
end
WEB --> GATEWAY
MOB --> GATEWAY
API_CLIENT --> GATEWAY
GATEWAY --> AUTH_SVC
GATEWAY --> USER_SVC
AUTH_SVC --> POSTGRES
AUTH_SVC --> REDIS
USER_SVC --> POSTGRES
USER_SVC --> S3
AUTH_SVC --> QUEUE
USER_SVC --> QUEUE
QUEUE --> NOTIF_SVC
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.
- 5d ago First seen · 477 lines · 15 tokens per session scan B e36c59f2eef2
agent-architecture is a skill published in the GitHub repository ruvnet/ruflo (70,498 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 2,601 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
external-memory-plugin
Develop, adapt, review, test, and troubleshoot Nexent external memory provider plugins, including plugin.yaml manifests, searchable and ingestible provider protocols, error mapping, network-isolated unit tests, deployment configuration, and Mem0-based examples. Use when adding a new external memory vendor, changing an…
nw-design
Designs system architecture with C4 diagrams and technology selection. Routes to the right architect based on design scope (system, domain, application, or full stack). Two interaction modes: guide (collaborative Q&A) or propose (architect presents options with trade-offs).
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
repo-genome
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.
score-harness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.