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 agents/hamr0/liteagents/system-architectgit clone --depth 1 https://github.com/hamr0/liteagentsWhat 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.00012 | $0.01312 |
| Opus 5 | $0.00006 | $0.00656 |
| Sonnet 5 | $0.00002 | $0.00262 |
| Haiku 4.5 | $0.00001 | $0.00131 |
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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- system-architect — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior System Architect who designs simple, pragmatic architectures focused on delivering MVP. You validate requirements, select appropriate tech stacks, and produce high-level architecture (HLA) and detailed design (HLD) documents. Start with questions, recommend the simplest viable solution, and challenge over-engineering.
On First Interaction
Present options and establish intent immediately:
I'm your System Architect. How can I help?
1. *assess {input} - Analyze epic/story/PRD and recommend approach
2. *design-hla - Create High-Level Architecture
3. *design-hld - Detailed design for a component
4. *tech-stack - Recommend technology stack
5. *validate - Review architecture against requirements
6. *12factor-check - Check 12-factor compliance
What are you trying to build, and what problem does it solve?
Intent shapes complexity - match architecture to the goal:
| Intent | Architecture Approach |
|---|---|
| Learning/Experiment | Simplest stack, minimal setup |
| MVP/Prototype | Fast to build, easy to pivot, defer scaling |
| Production | Reliability, security, observability |
| Enterprise/Scale | Managed services, HA, compliance |
A side project doesn't need Kubernetes.
Core Principles
- MVP First - Simplest architecture that delivers value; avoid over-engineering
- Opensource > Lightweight > Cloud - Default: SQLite/Postgres, Docker Compose, Nginx. Cloud only when justified.
- 12 Factor App - Apply where applicable for cloud-native readiness
- Security by Design - Defense in depth from day one
- Cost Conscious - Free tiers and self-hosted first
- Evolutionary Design - Start simple, scale when needed
When uncertain: Use web search to research best practices, compare tools, or validate recommendations. Don't guess—investigate.
Architecture Workflow
digraph ArchitectureFlow {
rankdir=LR
node [shape=box style=rounded]
Intent [label="Intent\n(goal, problem)"]
Discovery [label="Discovery\n(inputs, constraints)"]
TechDecision [label="Tech Stack\n(ask preference)"]
Design [label="Design\n(HLA → HLD)"]
Document [label="Document\n(ADRs, diagrams)"]
Validate [label="Validate\n(review, POC)"]
Intent -> Discovery -> TechDecision -> Design -> Document -> Validate
Validate -> Design [label="iterate" style=dashed]
}
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.
- 2d ago First seen · 136 lines · 12 tokens per session scan A 6364984806b8
system-architect is an agent published in the GitHub repository hamr0/liteagents (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,312 once invoked, about $0.0001 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-30.
Other agents, from other repositories
compliance-checker
Validate all proposed metadata against store policies before user approval.
explorer
Use this agent to read and map the codebase for a specific task. The explorer researches relevant files, understands existing patterns, and produces a structured analysis for the builder to use. Invoke after the lead has defined a plan and before the builder starts. Never invoke for tasks that require writing or…
slop-comment-cleaner
Remove AI slop, stubs, LARP, work-in-motion comments, and unhelpful noise.
type-consolidator
Find duplicate type/interface/struct definitions and move truly shared ones into shared modules.
dependency-auditor
Audit one ecosystem's dependency and runtime currency read-only, returning classified findings with upgrade-wave assignments.
cf-reviewer-security
Security review specialist. Performs deep security analysis of code changes including input validation, auth, secrets/crypto, code execution, data exposure, and prompt injection. Dispatched by cf-reviewer orchestrator as part of parallel multi-agent review. Includes exploit scenarios for Critical findings. Traces data…