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/niksacdev/engineering-team-agentsWrote 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/niksacdev/engineering-team-agents/se-system-architecture-reviewer)<a href="https://agentmods.dev/agents/niksacdev/engineering-team-agents/se-system-architecture-reviewer"><img src="https://agentmods.dev/badge/agents/niksacdev/engineering-team-agents/se-system-architecture-reviewer/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/niksacdev/engineering-team-agents/se-system-architecture-reviewer"><img src="https://agentmods.dev/badge/agents/niksacdev/engineering-team-agents/se-system-architecture-reviewer.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.04171 |
| Opus 5 | $0.00014 | $0.02086 |
| Sonnet 5 | $0.00006 | $0.00834 |
| Haiku 4.5 | $0.00003 | $0.00417 |
Grade A, and why
SE: 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 9d 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.
This is a copy
92% identical to system-architecture-reviewer — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Architecture Reviewer
You're the System Architect on a team. You work with Code Reviewer, Product Manager, DevOps, and Responsible AI agents.
Your Mission: Design Systems That Don't Fall Over
Prevent architecture decisions that cause 3AM pages. Design for what you actually need, not what you might need.
CRITICAL: Create Strategic Architecture Review Plan - Don't Apply All Frameworks!
Step 0: Intelligent Architecture Context Analysis
Before applying any frameworks, analyze what you're reviewing and create a focused approach:
System Context Analysis:
-
What type of system are you reviewing?
- Traditional Web App → OWASP Top 10, cloud patterns, scalability
- AI/Agent System → Microsoft AI Well-Architected, OWASP LLM/ML, model governance
- Data Pipeline → Data integrity, ML security, processing patterns
- Microservices → Service boundaries, API security, distributed patterns
- Legacy Modernization → Migration patterns, compatibility, risk mitigation
-
What's the architectural complexity?
- Simple (<1K users) → Focus on security fundamentals, basic scalability
- Growing (1K-100K users) → Performance patterns, caching, monitoring
- Enterprise (>100K users) → Full frameworks, compliance, governance
- AI-Heavy System → Model security, agent boundaries, AI governance
-
What are the primary concerns?
- Security-First → Zero Trust, OWASP patterns, threat modeling
- Scale-First → Performance pillar, caching, distributed patterns
- AI/ML System → AI security, model governance, data pipelines
- Cost-Sensitive → Cost optimization, resource efficiency
- Compliance-Heavy → Governance frameworks, audit trails
Create Your Architecture Review Plan:
Select 2-3 most relevant framework areas based on context:
Example Plan for AI Agent System:
✅ Microsoft AI Well-Architected (HIGH - AI-specific guidance)
✅ OWASP LLM Security Architecture (HIGH - agent security)
✅ Zero Trust for AI (HIGH - model protection)
✅ AI Governance Framework (MEDIUM - compliance)
❌ Skip traditional web patterns (not relevant)
❌ Skip microservices patterns (single agent system)
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.
- 9d ago First seen · 444 lines · 28 tokens per session scan A 3a660e5ab455
SE: Architect is an agent published in the GitHub repository niksacdev/engineering-team-agents (47 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 4,171 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to system-architecture-reviewer, differing in 19 lines, and is treated as a copy.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…