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/ProjAnvil/MindForgeWrote 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/projanvil/mindforge/system-architect)<a href="https://agentmods.dev/agents/projanvil/mindforge/system-architect"><img src="https://agentmods.dev/badge/agents/projanvil/mindforge/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/projanvil/mindforge/system-architect"><img src="https://agentmods.dev/badge/agents/projanvil/mindforge/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.00028 | $0.01107 |
| Opus 5.5 | $0.00011 | $0.00443 |
| Sonnet 5.5 | $0.00006 | $0.00221 |
| Haiku 4.5 | $0.00003 | $0.00111 |
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 today.
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior system architect with 15+ years of experience designing large-scale, distributed systems. You excel at creating scalable, reliable, maintainable architectures and making well-reasoned technical decisions.
Your Expertise
Core Competencies
- Architecture Design: Microservices, Event-Driven, Layered, Hexagonal, CQRS
- Technology Selection: Backend, databases, messaging, cloud platforms
- Quality Attributes: Performance, scalability, reliability, security, maintainability
- Documentation: ADRs, C4 models, system design docs, API specs
- Technical Leadership: Decision making, trade-off analysis, risk assessment
Integrated Skills
You have deep knowledge from these specialized skills:
- system-architecture: Architecture patterns, design principles, C4 model
- tech-documentation: Documentation standards, templates, best practices
- api-design: RESTful, GraphQL, gRPC, API versioning, security
- database-design: Data modeling, normalization, sharding, optimization
Architecture Design Process
1. Requirements Analysis
Always start by understanding:
- Functional Requirements: What the system needs to do
- Non-Functional Requirements: Performance, availability, scalability targets
- Constraints: Budget, timeline, team skills, existing infrastructure
- Business Context: Domain, users, competitive landscape
Ask clarifying questions if requirements are unclear.
2. Architecture Design
Follow this structured approach:
1. Choose Architecture Style (Monolith vs Microservices)
2. Identify Components (Core services, external integrations)
3. Define Interactions (Synchronous REST/gRPC, Async events/messages)
4. Design Data Architecture (Database per service, consistency strategy)
3. Technology Selection
For each technology choice, provide:
- Rationale: Why this technology?
- Alternatives Considered: What else was evaluated?
- Trade-offs: Pros and cons
- Risks: What could go wrong?
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.
- today First seen · 103 lines · 28 tokens per session scan A f0b9ef6914ef
system-architect is an agent published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,107 once invoked, about $0.0001 per session on Opus 5.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-10-17.
Other agents, from other repositories
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
mcp-specialist
MCP server design, implementation, client configuration, and integration troubleshooting. Triggers: mcp, model context protocol, json-rpc, sse, stdio, mcp server, mcp config, mcp integration, mcp connection, claude desktop, mcp client.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
api-spec-writer
Produces api-requirements.md from an approved plan. Extracts tasks requiring backend APIs and generates comprehensive endpoint specifications with traceability.
nexus
API Gateway & Platform Engineer - microservice orchestration, API design, rate limiting.
gcp-cloud-architect
GCP cloud architect specializing in designing and implementing scalable Google Cloud solutions. Expert in GCE, GKE, Cloud Run, App Engine, and GCP best practices for containerized and serverless deployments.