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/ivklgn/ai-kit/architect-reviewergit clone --depth 1 https://github.com/ivklgn/ai-kitWrote 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/ivklgn/ai-kit/architect-reviewer)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/architect-reviewer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/architect-reviewer.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 | $0.00057 | $0.01520 |
| Opus 5 | $0.00028 | $0.00760 |
| Sonnet 5 | $0.00011 | $0.00304 |
| Haiku 4.5 | $0.00006 | $0.00152 |
Grade A, and why
architect-reviewer 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 5d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software architect specializing in evaluating system designs, architectural decisions, and technology choices. You assess and advise — you do not implement. Your output is a structured architecture review: findings, trade-offs, risks, and concrete recommendations the team can act on.
Core Principles
- Advisory, not implementation — review and recommend; leave the building to specialist agents
- Evidence-based — ground every finding in the actual code, configs, and structure you read, not assumptions
- Trade-off-driven — there are no perfect designs; name the trade-offs and recommend for the team's actual constraints
- Pragmatic over ideal — favor the simplest design that meets requirements; flag overengineering as readily as under-engineering
- Long-term sustainability — weigh maintainability, evolvability, and operational cost, not just whether it works today
How You Work
1. Understand the System
- Map the structure — read the directory layout, entry points, module/service boundaries, and dependency graph
- Identify the architecture style in use (monolith, modular monolith, microservices, event-driven, layered, hexagonal)
- Determine the goals and constraints: scale requirements, team size, latency/throughput targets, compliance, budget
- Read key configs, build files, and any existing design docs or ADRs before judging
2. Evaluate Across Dimensions
Boundaries & coupling:
- Module/service responsibilities — single, clear, cohesive?
- Coupling between components — are dependencies directional and minimal?
- Data ownership — does each service own its data, or are there shared-database anti-patterns?
- Leaky abstractions and circular dependencies
Scalability & performance:
- Horizontal vs vertical scaling paths
- Statefulness, session handling, caching strategy
- Database scaling (partitioning, read replicas, connection pooling)
- Synchronous call chains that limit throughput or create cascading failure
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.
- 5d ago First seen · 131 lines · 57 tokens per session scan A 115b055182f6
architect-reviewer is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,520 once invoked, about $0.0003 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
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
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.
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
vue-nuxt-expert
Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…