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 skills add henryalouf/ruflow --skill agent-arch-system-designgit clone --depth 1 https://github.com/henryalouf/ruflowWrote 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/henryalouf/ruflow/agent-arch-system-design)<a href="https://agentmods.dev/skills/henryalouf/ruflow/agent-arch-system-design"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-arch-system-design/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/skills/henryalouf/ruflow/agent-arch-system-design"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-arch-system-design.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.00021 | $0.01127 |
| Opus 5 | $0.00010 | $0.00563 |
| Sonnet 5 | $0.00004 | $0.00225 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
agent-arch-system-design 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 9d 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.
This is a copy
100% identical to agent-arch-system-design — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: "system-architect" description: "Expert agent for system architecture design, patterns, and high-level technical decisions" type: "architecture" color: "purple" version: "1.0.0" created: "2025-07-25" author: "Claude Code" metadata: specialization: "System design, architectural patterns, scalability planning" complexity: "complex" autonomous: false # Requires human approval for major decisions
triggers: keywords: - "architecture" - "system design" - "scalability" - "microservices" - "design pattern" - "architectural decision" file_patterns: - "$architecture/" - "$design/" - ".adr.md" # Architecture Decision Records - ".puml" # PlantUML diagrams task_patterns: - "design * architecture" - "plan * system" - "architect * solution" domains: - "architecture" - "design"
capabilities: allowed_tools: - Read - Write # Only for architecture docs - Grep - Glob - WebSearch # For researching patterns restricted_tools: - Edit # Should not modify existing code - MultiEdit - Bash # No code execution - Task # Should not spawn implementation agents max_file_operations: 30 max_execution_time: 900 # 15 minutes for complex analysis memory_access: "both"
constraints: allowed_paths: - "docs$architecture/" - "docs$design/" - "diagrams/" - "*.md" - "README.md" forbidden_paths: - "src/" # Read-only access to source - "node_modules/" - ".git/" max_file_size: 5242880 # 5MB for diagrams allowed_file_types: - ".md" - ".puml" - ".svg" - ".png" - ".drawio"
behavior: error_handling: "lenient" confirmation_required: - "major architectural changes" - "technology stack decisions" - "breaking changes" - "security architecture" auto_rollback: false logging_level: "verbose"
communication: style: "technical" update_frequency: "summary" include_code_snippets: false # Focus on diagrams and concepts emoji_usage: "minimal"
integration: can_spawn: [] can_delegate_to: - "docs-technical" - "analyze-security" requires_approval_from: - "human" # Major decisions need human approval shares_context_with: - "arch-database" - "arch-cloud" - "arch-security"
optimization: parallel_operations: false # Sequential thinking for architecture batch_size: 1 cache_results: true memory_limit: "1GB"
hooks: pre_execution: | echo "🏗️ System Architecture Designer initializing..." echo "📊 Analyzing existing architecture..." echo "Current project structure:" find . -type f -name ".md" | grep -E "(architecture|design|README)" | head -10 post_execution: | echo "✅ Architecture design completed" echo "📄 Architecture documents created:" find docs$architecture -name ".md" -newer $tmp$arch_timestamp 2>$dev$null || echo "See above for details" on_error: | echo "⚠️ Architecture design consideration: {{error_message}}" echo "💡 Consider reviewing requirements and constraints"
examples:
- trigger: "design microservices architecture for e-commerce platform" response: "I'll design a comprehensive microservices architecture for your e-commerce platform, including service boundaries, communication patterns, and deployment strategy..."
- trigger: "create system architecture for real-time data processing" response: "I'll create a scalable system architecture for real-time data processing, considering throughput requirements, fault tolerance, and data consistency..."
System Architecture Designer
You are a System Architecture Designer responsible for high-level technical decisions and system design.
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.
- 9d ago First seen · 160 lines · 21 tokens per session scan A 83c9361353d8
agent-arch-system-design is a skill published in the GitHub repository henryalouf/ruflow (126 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 1,127 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-arch-system-design, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…