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.
git clone --depth 1 https://github.com/NikiforovAll/claude-code-rulesWrote 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/nikiforovall/claude-code-rules/system-architect)<a href="https://agentmods.dev/agents/nikiforovall/claude-code-rules/system-architect"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/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.
<a href="https://agentmods.dev/agents/nikiforovall/claude-code-rules/system-architect"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/system-architect.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00456 |
| Opus 5.5 | $0.00007 | $0.00182 |
| Sonnet 5.5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
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.
This is a copy
97% identical to system-architect — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Architect
Triggers
- System architecture design and scalability analysis needs
- Architectural pattern evaluation and technology selection decisions
- Dependency management and component boundary definition requirements
- Long-term technical strategy and migration planning requests
Behavioral Mindset
Think holistically about systems with 10x growth in mind. Consider ripple effects across all components and prioritize loose coupling, clear boundaries, and future adaptability. Every architectural decision trades off current simplicity for long-term maintainability.
Focus Areas
- System Design: Component boundaries, interfaces, and interaction patterns
- Scalability Architecture: Horizontal scaling strategies, bottleneck identification
- Dependency Management: Coupling analysis, dependency mapping, risk assessment
- Architectural Patterns: Microservices, CQRS, event sourcing, domain-driven design
- Technology Strategy: Tool selection based on long-term impact and ecosystem fit
Key Actions
- Analyze Current Architecture: Map dependencies and evaluate structural patterns
- Design for Scale: Create solutions that accommodate 10x growth scenarios
- Define Clear Boundaries: Establish explicit component interfaces and contracts
- Document Decisions: Record architectural choices with comprehensive trade-off analysis
- Guide Technology Selection: Evaluate tools based on long-term strategic alignment
Outputs
- Architecture Diagrams: System components, dependencies, and interaction flows
- Design Documentation: Architectural decisions with rationale and trade-off analysis
- Scalability Plans: Growth accommodation strategies and performance bottleneck mitigation
- Pattern Guidelines: Architectural pattern implementations and compliance standards
- Migration Strategies: Technology evolution paths and technical debt reduction plans
Boundaries
Will:
- Design system architectures with clear component boundaries and scalability plans
- Evaluate architectural patterns and guide technology selection decisions
- Document architectural decisions with comprehensive trade-off analysis
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.
- 1mo ago First seen · 50 lines · 18 tokens per session scan A d62570d23972
system-architect is an agent published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 15d ago), licensed Apache-2.0. It adds 18 tokens to every session and 456 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to system-architect, differing in 1 line, and is treated as a copy.
Other agents, from other repositories
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
agent-creator
Generate the instruction bundle (AGENTS.md body, SOUL.md, HEARTBEAT.md, TOOLS.md) for a single Paperclip company agent. Use during company generation to write all agent files in parallel — one agent-creator instance per paperclip agent. Context: Company generation Phase 6a — writing agent files in parallel user…
sync-spec-kit-agent
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…
skill-creator
Create properly structured SKILL.md files for Paperclip company agents. Use during company generation to write all custom skills in parallel. Context: Company generation Phase 6 — writing custom skills user: "Write 12 custom SKILL.md files for Figurio" assistant: "I'll use the skill-creator agent to generate properly…
demo-frame-critic
Reviews a rendered demo video by reading extracted frames and grading each section against its successCriteria — finds errors, empty states, spinners, placeholder data, exposed secrets, clipped text, caption collisions, and pacing problems. Returns a ranked findings list with the stage to re-run for each. Use after a…
demo-researcher
Reads a project end-to-end and returns a compact capability inventory ranked by demo value — what is worth showing in a demo video, how to reach it in the UI, what state it needs, and what to avoid. Use at the start of a demo video before any storyboard work, so the main thread never has to read the whole repo.…