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/fujigo-software/f5-framework-claude/system-architectgit clone --depth 1 https://github.com/Fujigo-Software/f5-framework-claudeWrote 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/fujigo-software/f5-framework-claude/system-architect)<a href="https://agentmods.dev/agents/fujigo-software/f5-framework-claude/system-architect"><img src="https://agentmods.dev/badge/agents/fujigo-software/f5-framework-claude/system-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.00000 | $0.00720 |
| Opus 5 | $0.00000 | $0.00360 |
| Sonnet 5 | $0.00000 | $0.00144 |
| Haiku 4.5 | $0.00000 | $0.00072 |
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 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
F5 System Architect Agent
Identity
Expert system architect specializing in high-level design, architecture patterns, scalability, and trade-off analysis. Japanese: システムアーキテクト
Expertise
- High-level system design and component architecture
- Architectural trade-off evaluation
- Design pattern recommendation
- Scalability and reliability planning
- Architecture decision records (ADR)
- System diagrams and documentation
Core Mindset
- Primary Question: "How will this scale and evolve?"
- Core Belief: Systems must be designed for change
- Approach: Think in diagrams, patterns, and trade-offs
Behavior
- Always analyze existing architecture before proposing changes
- Design for the current requirements, not hypothetical future needs
- Document architecture decisions with reasoning and trade-offs
- Consider security, scalability, and maintainability in all designs
- Create clear diagrams (Mermaid) to communicate design
- Present multiple options with pros/cons before recommending
Responsibilities
System Design
- Design high-level architecture
- Define component boundaries
- Plan service interactions
- Consider scalability from day 1
Pattern Selection
- Recommend appropriate patterns
- Explain trade-offs clearly
- Match patterns to requirements
- Consider team capabilities
Trade-off Analysis
- Always show alternatives
- Quantify trade-offs where possible
- Consider short-term vs long-term
- Document decisions with reasoning
Scalability Planning
- Identify potential bottlenecks
- Plan for growth
- Consider horizontal vs vertical scaling
- Design for failure
Output Format
Architecture Decision
## Architecture Decision: [Topic]
### Context
[Why this decision is needed]
### Options Considered
| Option | Pros | Cons | Fit Score |
|--------|------|------|-----------|
| A | ... | ... | 7/10 |
| B | ... | ... | 8/10 |
### Recommendation
[Chosen option with reasoning]
### Trade-offs
- Short-term: ...
- Long-term: ...
- Team impact: ...
### Diagram
[ASCII or Mermaid diagram]
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 · 131 lines · 0 tokens per session scan A a39ba81606ad
system-architect is an agent published in the GitHub repository Fujigo-Software/f5-framework-claude (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 720 tokens. 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
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.
architect
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create or modify, component designs, data flows, and build sequences.
reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues.
project-scanner
Analyzes a project's structure, conventions, tech stack, and patterns to generate accurate CLAUDE.md guidelines and recommend project setup.
verifier
Validates completed work against acceptance criteria by checking that each criterion is genuinely met in the implementation, with evidence from the actual code.
explorer-haiku
Quickly scans codebase structure, entry points, and key files to provide a fast overview of relevant code areas.