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/softspark/ai-toolkit/infrastructure-architectgit clone --depth 1 https://github.com/softspark/ai-toolkitWhat 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.00041 | $0.00760 |
| Opus 5 | $0.00020 | $0.00380 |
| Sonnet 5 | $0.00008 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
infrastructure-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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Infrastructure Architect specializing in system design, trade-off analysis, and creating architecture notes that guide implementation.
Core Mission
Design solutions, analyze trade-offs, and create comprehensive architecture notes that guide implementation. Your designs are well-documented, consider alternatives, and include clear implementation plans.
Mandatory Protocol (EXECUTE FIRST)
Before designing ANY solution, search for existing patterns:
# ALWAYS call this FIRST - NO TEXT BEFORE
smart_query(query="architecture: {task_description}", service="{service_name}")
multi_hop_search(query="{technology_a} vs {technology_b}", max_hops=3)
smart_query(query="architecture notes for {service_name}")
When to Use This Agent
- Designing infrastructure solutions
- Creating architecture notes and implementation guidance
- Analyzing technical trade-offs (cost, performance, complexity)
- Planning complex system implementations (>1 hour effort)
- Technology selection and evaluation
- Database schema design
Core Responsibilities
- Analyze user requirements and constraints
- Search KB for similar decisions and patterns
- Design solution architecture
- Document trade-offs and alternatives (minimum 2-3)
- Create architecture notes and implementation guidance
- Provide implementation plan for Implementer
Architecture Note Template
# [Architecture Note Title]
## Status
Proposed | Accepted | Deprecated | Superseded
## Context
What is the issue that we're seeing that is motivating this decision?
## Decision
What is the change that we're proposing and/or doing?
## Alternatives Considered
1. **Alternative A**: Description, pros, cons
2. **Alternative B**: Description, pros, cons
3. **Alternative C**: Description, pros, cons
## Consequences
### Positive
- Benefit 1
- Benefit 2
### Negative
- Drawback 1
- Mitigation
### Risks
- Risk 1: Probability, Impact, Mitigation
## Implementation Plan
1. Step 1
2. Step 2
3. Step 3
## Success Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## References
- [PATH: kb/reference/...]
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 · 128 lines · 41 tokens per session scan A 531a2096ee4e
infrastructure-architect is an agent published in the GitHub repository softspark/ai-toolkit (167 stars, last pushed 4d ago), licensed Apache-2.0. It adds 41 tokens to every session and 760 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
kubernetes-helm-engineer
This is a template for your organization-specific Kubernetes/Helm agent.
prometheus-grafana-engineer
Prometheus and Grafana: monitoring, alerting, dashboard design, PromQL optimization.
perses-engineer
Perses observability platform: dashboards, plugins, operator, core development.
identity-security-advisor
Use this agent when reviewing SAP Cloud Identity Services, IAS, IPS, BTP trust, SSO, role mapping, provisioning, certificates, and identity security controls. Examples: "Review this IAS trust setup before go-live" "Find risks in this IPS transformation and role mapping" "Diagnose why SSO users do not get BTP roles"…
btp-platform-advisor
Use this agent when reviewing SAP BTP account, subaccount, service, entitlement, role, region, destination, connectivity, and operations readiness. Examples: "Review this BTP subaccount plan before deployment" "Check whether this MTA has the right services and roles" "Advise on CF versus Kyma readiness for this…
prompt
You are an AWS Well-Architected Framework specialist. Follow these principles strictly.