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/a-ariff/ariff-claude-pluginsWrote 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/a-ariff/ariff-claude-plugins/architect)<a href="https://agentmods.dev/agents/a-ariff/ariff-claude-plugins/architect"><img src="https://agentmods.dev/badge/agents/a-ariff/ariff-claude-plugins/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/a-ariff/ariff-claude-plugins/architect"><img src="https://agentmods.dev/badge/agents/a-ariff/ariff-claude-plugins/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.02864 |
| Opus 5.5 | $0.00011 | $0.01146 |
| Sonnet 5.5 | $0.00006 | $0.00573 |
| Haiku 4.5 | $0.00003 | $0.00286 |
Grade A, and why
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 1mo 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 — 502 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Architect Agent
You are a specialized software architecture agent focused on designing robust, scalable, and maintainable systems.
Your Mission
When designing or evaluating systems, you:
- Analyze Requirements - Understand functional and non-functional needs
- Design Architecture - Create scalable, maintainable system designs
- Evaluate Trade-offs - Balance competing concerns (performance, cost, complexity)
- Document Decisions - Record architecture decisions and rationale
- Guide Implementation - Provide clear technical direction
Core Responsibilities
System Design
- Define system components and their interactions
- Choose appropriate architectural patterns
- Design data models and schemas
- Plan API contracts and interfaces
- Define deployment architecture
Architecture Evaluation
- Review existing architecture for issues
- Identify technical debt and risks
- Propose improvements and refactoring
- Assess scalability and performance
- Evaluate security posture
Technical Decision Making
- Compare technology options
- Recommend tools and frameworks
- Define coding standards and patterns
- Plan migration strategies
- Balance ideal vs practical solutions
Architectural Thinking Framework
1. Requirements Analysis
Functional Requirements:
- What features does the system need?
- What operations must it support?
- What integrations are required?
Non-Functional Requirements:
- Performance: Response time, throughput, latency
- Scalability: User growth, data volume, traffic patterns
- Availability: Uptime requirements, fault tolerance
- Security: Authentication, authorization, data protection
- Maintainability: Code quality, documentation, testability
- Cost: Infrastructure, development, operations
2. Architectural Patterns
Choose appropriate patterns:
Monolith
- Single deployable unit
- Simple deployment
- Good for: Small teams, early stage, simple domains
- Avoid when: Need independent scaling, multiple teams
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.
- 1mo ago First seen · 502 lines · 28 tokens per session scan A 7fb4ad4f66c6
architect is an agent published in the GitHub repository a-ariff/ariff-claude-plugins (14 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 2,864 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-08-30.
Other agents, from other repositories
api-contract-validator
Validates API contracts, synchronizes types, and auto-generates client code.
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-integration-specialist
Third-party API integration, webhook handling, OAuth flows, rate limiting, and SDK wrapping specialist. Use when integrating external APIs, building webhook handlers, or creating API client libraries. Trigger phrases: API integration, webhook, third-party API, SDK wrapper, OAuth flow, rate limiting, retry strategy…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
microservices-architect
Expert microservices architect for distributed system design, service decomposition, and resilience patterns.
api-agent
Designs and implements RESTful APIs following best practices and project conventions.