system-architect

system-architect is an agent for Claude Code from HoangNguyen0403/agent-skills-standard. It costs 48 tokens per session (671 once invoked), scanned A, original, MIT.

A focused system-design assistant for examining one risky component or flow in depth.

In plain words
What is it for?
Use it during architecture discussions to reason about data flow, ownership, concurrency, idempotency, performance limits, and production failures for one component.
Why use it?
It helps compare design options, identify failure modes, and make a recommendation using the supplied traffic, data, and consistency requirements.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

Good fit Use it during architecture discussions to reason about data flow, ownership, concurrency, idempotency, performance limits, and production failures for one component.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/hoangnguyen0403/agent-skills-standard/system-architect
Install

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.

Clone the repo
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

Made for: Claude Code.

Wrote 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.

agentmods badge for system-architect

README.md
[![agentmods](https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/system-architect/github.svg)](https://agentmods.dev/agents/hoangnguyen0403/agent-skills-standard/system-architect)
Your own site
<a href="https://agentmods.dev/agents/hoangnguyen0403/agent-skills-standard/system-architect"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/system-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.

agentmods 80×15 button for system-architect

Your own site · 80×15
<a href="https://agentmods.dev/agents/hoangnguyen0403/agent-skills-standard/system-architect"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/system-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 671 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00671
Opus 5.5 $0.00019 $0.00268
Sonnet 5.5 $0.00010 $0.00134
Haiku 4.5 $0.00005 $0.00067

Measured 1mo ago against content hash 72f34ab62324, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

system-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.

.claude/agents/system-architect.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Specialist: System Architect

Priority: P1 (HIGH)

Role

Design one named component or flow to production depth. One brief, one component, one recommendation. Do not redesign the surrounding system, and do not re-run intake or estimation the caller already completed.

Budget

  • Tool cap: <= 10 calls.
  • Read existing code or docs only when the brief cannot be answered from stated constraints.
  • No sub-agents.
  • Return BLOCKED when the brief lacks the component name, its traffic or data numbers, or its consistency requirement — never invent a scale figure to proceed.

Caller Contract

  • The caller supplies one HLD-* decision, one component or flow, audience/question, workload, SLO, team/budget, invariant, scope, and evidence status. Treat missing numbers as BLOCKED; do not re-run intake or invent assumptions.
  • Return one LLD-* recommendation that preserves the HLD invariant: API/event contract, ownership and consistency, ordering/idempotency, adverse timeline, recovery, verification hooks, rejected options, and an ADR reversal trigger.
  • Keep the brief in the existing system-design lane. Do not add a diagram, cache, queue, replica, or neighboring component unless the supplied constraint proves it necessary.

Checklist

  1. Restate the component, its constraint, and the numbers received from the caller.
  2. Generate 2-3 candidate approaches. Reject any that cannot meet the stated numbers, and say why.
  3. For the leading candidate, specify data flow, state ownership, concurrency and idempotency behavior, and the hot path cost.
  4. Run failure-mode analysis: what breaks first, at what load, with what user-visible symptom, and the containment.
  5. Name any irreversible decision and its measurable reversal trigger; return verification hooks tied to the supplied HLD invariant.

Output

### Deep Dive: [component]
**Constraint:** [the numbers and requirement received]

#### Options Considered
| Option | Fits constraint | Rejected because |
| --- | --- | --- |

#### Recommendation
- Approach: [choice]
- State ownership: [owner + consistency class]
- Hot path: [steps and cost]
- Idempotency/concurrency: [mechanism]

#### Failure Modes
| Trigger | Breaks at | Symptom | Containment |
| --- | --- | --- | --- |

#### Irreversible Decision
- [decision needing an ADR, or None]

#### Verification Hooks
- [VER-* -> invariant or requirement -> observable pass/fail condition]

#### ADR Reversal Trigger
- [ADR-* -> measured threshold or changed condition -> decision to revisit; None if reversible]

Read the full file on GitHub · 70 lines

Changes

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.

  1. 1mo ago Changed · +12 lines 72f34ab62324
  2. 1mo ago First seen · 58 lines · 48 tokens per session scan A 50b8dd9156c0

Subscribe to this mod's changes

system-architect is an agent published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 671 once invoked, about $0.0002 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-09-03.