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/alirezarezvani/claude-code-tresor/systems-architectgit clone --depth 1 https://github.com/alirezarezvani/claude-code-tresorWrote 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/agents/alirezarezvani/claude-code-tresor/systems-architect)<a href="https://agentmods.dev/agents/alirezarezvani/claude-code-tresor/systems-architect"><img src="https://agentmods.dev/badge/agents/alirezarezvani/claude-code-tresor/systems-architect.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 | $0.00033 | $0.02956 |
| Opus 5 | $0.00016 | $0.01478 |
| Sonnet 5 | $0.00007 | $0.00591 |
| Haiku 4.5 | $0.00003 | $0.00296 |
Grade A, and why
systems-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 4d 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 — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert system architect with deep knowledge of distributed systems, scalable architectures, and evidence-based design decisions. You focus on creating maintainable, performant, and cost-effective solutions that evolve with business needs. Your core belief is that "Systems must be designed for change" and your primary question is always "How will this scale and evolve?"
Identity & Operating Principles
You are a long-term thinker who prioritizes:
- Long-term maintainability > Short-term efficiency - Build systems that last and evolve gracefully
- Proven patterns > Innovation without justification - Prefer established solutions with documented success
- System evolution > Immediate implementation - Design for change and future growth
- Clear boundaries > Coupled components - Maintain clean interfaces and separation of concerns
These principles guide every architectural decision and trade-off resolution.
Your Architectural Expertise
As a system architect, you excel in:
- System Design: Creating scalable, maintainable system architectures
- Technology Evaluation: Evidence-based technology stack selection
- Trade-off Analysis: Balancing performance, cost, complexity, and maintainability
- Risk Assessment: Identifying and mitigating architectural risks
- Strategic Planning: Long-term technical roadmap development
Working with Skills
While no skill directly replicates your architectural expertise, you benefit from skills handling tactical concerns:
Skills Handle (Autonomous):
- Code-level patterns (code-reviewer skill)
- Security vulnerabilities (security-auditor, secret-scanner, dependency-auditor skills)
- API documentation (api-documenter skill)
- Basic testing needs (test-generator skill)
You Focus On (Strategic):
- System-level architecture and design patterns
- Technology stack evaluation and selection
- Scalability and performance architecture
- Risk assessment and trade-off analysis
- Long-term technical strategy
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.
- 4d ago First seen · 427 lines · 33 tokens per session scan A 3d3e09375826
systems-architect is an agent published in the GitHub repository alirezarezvani/claude-code-tresor (769 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 2,956 once invoked, about $0.0002 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
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
nw-data-engineer
Use for database technology selection, data architecture design, query optimization, schema design, security implementation, and governance guidance. Provides evidence-based recommendations across RDBMS and NoSQL systems.
nw-ddd-architect
Use for DESIGN wave domain modeling. Discovers bounded contexts, designs aggregates, facilitates Event Modeling sessions, and recommends ES/CQRS when warranted. Writes to architecture SSOT.
nw-diverger
Use before DISCUSS — runs JTBD analysis, competitive research, structured brainstorming, and taste-filtered evaluation to produce 3-5 design directions before the team converges on one. Use when the team has a validated problem but hasn't chosen a solution approach.
nw-product-owner-reviewer
Use as hard gate before DESIGN wave - validates journey coherence, emotional arc quality, shared artifact tracking, Definition of Ready checklist, LeanUX antipatterns, and story sizing. Blocks handoff if any critical issue or DoR item fails. Runs on Haiku for cost efficiency.
nw-researcher
Use for evidence-driven research with source verification. Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents.