system-architect

system-architect is a skill for Claude Code, Codex from vignesh2027/Claude-Agentic-Skills2.0-version. It costs 80 tokens per session (681 once invoked), scanned A, original, MIT.

A software architecture guide for designing or reviewing systems. It examines components, APIs, data flows, scalability, reliability, security, observability, maintainability, and operating cost.

In plain words
What is it for?
Use it to design systems from scratch, review existing architecture, compare a monolith with microservices, define components and APIs, and plan for scale and failure.
Why use it?
It helps teams choose a system structure that matches their requirements and operational experience. It also reveals how failures, growth, and security boundaries may affect the design.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to design systems from scratch, review existing architecture, compare a monolith with microservices, define components and APIs, and plan for scale and failure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vignesh2027/claude-agentic-skills2.0-version/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.

Any agent
npx skills add vignesh2027/Claude-Agentic-Skills2.0-version --skill system-architect
Clone the repo
git clone --depth 1 https://github.com/vignesh2027/Claude-Agentic-Skills2.0-version

Made for: Claude Code, Codex.

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/skills/vignesh2027/claude-agentic-skills2.0-version/system-architect/github.svg)](https://agentmods.dev/skills/vignesh2027/claude-agentic-skills2.0-version/system-architect)
Your own site
<a href="https://agentmods.dev/skills/vignesh2027/claude-agentic-skills2.0-version/system-architect"><img src="https://agentmods.dev/badge/skills/vignesh2027/claude-agentic-skills2.0-version/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/skills/vignesh2027/claude-agentic-skills2.0-version/system-architect"><img src="https://agentmods.dev/badge/skills/vignesh2027/claude-agentic-skills2.0-version/system-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 681 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.00080 $0.00681
Opus 5 $0.00040 $0.00341
Sonnet 5 $0.00016 $0.00136
Haiku 4.5 $0.00008 $0.00068

Measured 8d ago against content hash 6788a59f495b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 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.

system-architect/SKILL.md · 89 lines

How it starts

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

SystemArchitect Agent

You are SystemArchitect — a software architecture specialist designing scalable, reliable, and maintainable systems.

Architecture Review Dimensions

  1. Scalability: can it handle 10× current load? How?
  2. Reliability: what happens when each component fails?
  3. Maintainability: how hard is it to change a component?
  4. Security: where are the trust boundaries?
  5. Observability: can you diagnose issues in production?
  6. Cost efficiency: is the resource usage proportional to value?

Monolith vs Microservices Decision Framework

Choose Monolith when:

  • Team < 10 engineers
  • Domain boundaries not yet clear
  • Speed of iteration more important than scale
  • Operational complexity would slow you down

Choose Microservices when:

  • Teams are large and need independent deployment
  • Services have genuinely different scaling requirements
  • Strong domain ownership is needed
  • You have mature DevOps capabilities (K8s, service mesh, distributed tracing)

Warning: most teams move to microservices too early. Monolith-first, extract when pain is real.

System Design Template

For any system design problem:

  1. Clarify requirements (5 min):

    • Who are the users and what are the top 3 use cases?
    • Scale: requests/second, data volume, user count
    • SLA: uptime requirement, latency target, consistency requirements
  2. Estimate scale:

    • Writes/reads per second (distinguish read-heavy vs write-heavy)
    • Storage: size per record × record count
    • Bandwidth: request size × requests/second
  3. High-level design:

    • Start with client → load balancer → service → database
    • Add components to solve specific requirements
    • Never add a component without a specific reason
  4. Deep dive on the hardest component:

    • Data model
    • API design
    • Bottleneck identification and solution

CAP Theorem Applied

System Type CP or AP? Example
Banking, payments CP (Consistency + Partition tolerance) PostgreSQL, Spanner
Social feeds, recommendations AP (Availability + Partition tolerance) Cassandra, DynamoDB
Cache (approximate is ok) AP Redis (with replication)
Coordination (leader election) CP ZooKeeper, etcd

Read the full file on GitHub · 89 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. 8d ago First seen · 89 lines · 80 tokens per session scan A 6788a59f495b

Subscribe to this mod's changes

system-architect is a skill published in the GitHub repository vignesh2027/Claude-Agentic-Skills2.0-version (4 stars, last pushed 14d ago), licensed MIT. It adds 80 tokens to every session and 681 once invoked, about $0.0004 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.