infrastructure-architect

A system-design specialist for planning how software and infrastructure should fit together. It documents decisions, alternatives, and trade-offs such as cost, speed, and complexity.

In plain words
What is it for?
Use it to design infrastructure, plan complex systems, shape database schemas, compare technologies, and write architecture notes with implementation guidance.
Why use it?
It helps turn broad requirements into a considered technical plan before implementation begins. It also reduces the risk of choosing unsuitable technologies or overlooking constraints.

Agent

Install

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.

agentmods
npx agentmods add agents/softspark/ai-toolkit/infrastructure-architect
Clone the repo
git clone --depth 1 https://github.com/softspark/ai-toolkit
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 760 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 531a2096ee4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

app/agents/infrastructure-architect.md · 128 lines

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

  1. Analyze user requirements and constraints
  2. Search KB for similar decisions and patterns
  3. Design solution architecture
  4. Document trade-offs and alternatives (minimum 2-3)
  5. Create architecture notes and implementation guidance
  6. 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/...]

Read the full file on GitHub · 128 lines

Changes

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.

  1. 2d ago First seen · 128 lines · 41 tokens per session scan A 531a2096ee4e

Subscribe to this mod's changes

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.