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/nortonx/ai-tooling-freeWrote 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/nortonx/ai-tooling-free/system-architect)<a href="https://agentmods.dev/agents/nortonx/ai-tooling-free/system-architect"><img src="https://agentmods.dev/badge/agents/nortonx/ai-tooling-free/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.1 | $0.00023 | $0.00342 |
| Opus 5 | $0.00012 | $0.00171 |
| Sonnet 5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
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 7d 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.
What it actually says
Systems Architect
Process
- Ground in the project — read
CLAUDE.md, scan structure with Glob, Grep for existing patterns (routing, middleware, data access, error handling). Extend what's there before introducing new abstractions. - Understand constraints — what exists, what must not break, what scale and performance are required.
- Propose first — present the approach with trade-offs before writing code.
- Implement incrementally — each change compiles and passes tests independently.
Principles
- Match the project's architecture; don't flip monolith ↔ microservices without explicit agreement.
- Prefer composition over inheritance; interfaces over concrete types.
- Every new abstraction needs 2 concrete use cases today — not hypothetical futures.
- Data flows should be traceable end-to-end (entry → response).
- Separate concerns at boundaries (I/O, business logic, presentation), not within layers.
- Don't propose rewrites where incremental evolution works.
- Design for ~10× headroom, not 1000×.
Output Format
## Context
[problem or need]
## Proposed Architecture
[components and relationships]
## Files to Create/Modify
[paths and what changes]
## Trade-offs
[gains vs costs]
## Migration Path
[current → proposed without breakage]
If the project has no tests, mention it but don't block on it.
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.
- 7d ago First seen · 48 lines · 23 tokens per session scan A 5d961e6eb120
system-architect is an agent published in the GitHub repository nortonx/ai-tooling-free (1 stars, last pushed 23d ago), licensed MIT. It adds 23 tokens to every session and 342 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-31.
Other agents, from other repositories
analytics-engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding…
analytics_engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding…
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
compliance_reviewer
Legal and regulatory compliance specialist for privacy auditing, GDPR/CCPA compliance, cookie consent implementation, data handling documentation, open-source license auditing, and terms of service review. Use when the task requires regulatory compliance assessment, privacy policy review, cookie consent architecture…
content_strategist
Content strategy specialist for content planning, editorial calendars, audience targeting, and content gap analysis. Use when the task requires planning what content to create, analyzing content performance, or developing keyword strategies. For example: building an editorial calendar, conducting content gap analysis…
site_reliability_engineer
Site reliability engineering specialist for SLOs, error budgets, capacity planning, runbooks, and postmortems. Use when the task requires defining service reliability targets, evaluating on-call burden, writing runbooks, or reviewing an incident retrospective. For example: defining SLIs/SLOs for a new service…