Borrowing it
Nothing to install: this file belongs to getappz/agentflare. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/getappz/agentflare/master/.claude/skills/system-architecture-design/SKILL.mdgit clone --depth 1 https://github.com/getappz/agentflareWrote 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/getappz/agentflare/system-architecture-design)<a href="https://agentmods.dev/skills/getappz/agentflare/system-architecture-design"><img src="https://agentmods.dev/badge/skills/getappz/agentflare/system-architecture-design.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.00100 | $0.00816 |
| Opus 5 | $0.00050 | $0.00408 |
| Sonnet 5 | $0.00020 | $0.00163 |
| Haiku 4.5 | $0.00010 | $0.00082 |
Grade A, and why
system-architecture-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 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Architecture Design
Produce architecture decisions that explain why, not just what — diagrams and component lists go stale, but a documented trade-off analysis still answers "why did we do it this way" a year later.
When to use
- Designing service boundaries, a data model, or an API contract that other code will depend on and that's expensive to change once built.
- Evaluating a technology or pattern choice (microservices vs. monolith, sync vs. event-driven, SQL vs. NoSQL) where the wrong call is costly.
- Skip for changes scoped to a single module where the approach is already obvious — write the code, don't write an ADR for it.
Key responsibilities
- Design scalable, maintainable structure — not the most elaborate one that fits the requirements, the simplest one that does.
- Document the decision with the rationale, not just the conclusion.
- Produce diagrams that show component interactions and data flow.
- Evaluate real trade-offs between options, including "do nothing" and "the boring option."
- Account for operational concerns (deployment, monitoring, rollback) — architecture that's elegant to draw but painful to operate is a net loss.
Decision framework
Answer these before committing to a design, not after:
- What quality attributes actually matter here (throughput, consistency, latency, operability) — and which ones don't, so you're not over-building for them?
- What are the real constraints and assumptions (team size, existing infrastructure, deadline)?
- What are the trade-offs of each option under consideration — not just the chosen one?
- How does this align with (or complicate) existing architecture?
- What are the risks, and what's the mitigation or rollback plan if the decision turns out wrong?
Deliverables
- Architecture Decision Record (ADR) — the decision, the alternatives considered, and why this one won. Short-form is fine; the rationale is the point, not the ceremony.
- Component interaction diagram — who talks to whom, and how (sync call, event, shared store).
- Data flow diagram — where data originates, transforms, and lands.
- Technology evaluation (when applicable) — options compared against the actual requirements, not against feature checklists.
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 · 80 lines · 100 tokens per session scan A 88e2fb42f3a2
system-architecture-design is a skill published in the GitHub repository getappz/agentflare (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 100 tokens to every session and 816 once invoked, about $0.0005 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-31.
Other skills, from other repositories
code-review-pi
Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md. Use before committing changes.
goal-test
A local experiment for testing a goal command that keeps an AI coding session working until a stated condition is judged complete. It uses a separate language model to evaluate the conversation after each assistant turn.
relational-database-design
Designs or reviews a relational database schema for a given domain. Covers table structure, normalization, indexes, constraints, and migration strategy. Invoked when the user asks to design a schema, review a database structure, or optimize a data model.
sample-plugin
Sample plugin demonstrating the Skills + Tools model. Includes a Python tool (greeting) and a TypeScript tool (calculator).
codex-prompting
Internal guidance for composing prompts for Codex CLI models for coding, review, diagnosis, and research tasks inside the Codex Claude Code plugin.
openai-docs
Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting…