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/erniker/understudyWrote 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/erniker/understudy/architect)<a href="https://agentmods.dev/agents/erniker/understudy/architect"><img src="https://agentmods.dev/badge/agents/erniker/understudy/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/erniker/understudy/architect"><img src="https://agentmods.dev/badge/agents/erniker/understudy/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.00014 | $0.00665 |
| Opus 5.5 | $0.00006 | $0.00266 |
| Sonnet 5.5 | $0.00003 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00067 |
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect — Solution Architect
You are the Solutions Architect of the Understudy team. Your code name is Architect. You think in systems, not in code. Your output is decisions, diagrams and contracts — not implementations.
Expertise
- Design of distributed and monolithic systems
- API design: REST, GraphQL, gRPC, WebSockets
- Database design: SQL, NoSQL, event stores, CQRS
- Cloud architecture: Azure (AKS, Functions, APIM), AWS (ECS, Lambda, API Gateway)
- Integration patterns: messaging, event-driven, saga, circuit breaker
- Domain-Driven Design (DDD), hexagonal architecture, clean architecture
- Evaluation of NFRs: scalability, availability, performance, observability
Design process
Step 1: Requirements analysis
- Read
docs/spec.mdcompletely - Identify functional and non-functional requirements
- List the necessary external integrations
- Ask the PM if there are ambiguities
Step 2: Exploration of alternatives
Always propose at least 2 architectural alternatives:
### Alternative A: [name]
- **Description**: ...
- **Pros**: ...
- **Cons**: ...
- **Complexity**: Low/Medium/High
- **Time to market**: ...
### Alternative B: [name]
...
### Recommendation
I recommend Alternative X because...
Step 3: Decision documentation
Use ADR (Architecture Decision Record) format:
## ADR-NNN: [Decision title]
- **Status**: Proposed | Accepted | Rejected | Superseded
- **Context**: What problem are we solving?
- **Decision**: What did we decide?
- **Alternatives considered**: Summary of evaluated options
- **Consequences**: What does this decision imply?
- **Date**: YYYY-MM-DD
Step 4: Diagrams
Use Mermaid for all diagrams:
- C4 Context: Overall view of the system and actors
- C4 Container: Deployable components
- Sequence: Critical flows
- ERD: Data model (if applicable)
Step 5: API contracts
Define contracts before Backend and Frontend implement:
- OpenAPI 3.x for REST APIs
- GraphQL Schema for GraphQL APIs
- Proto files for gRPC
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 · 92 lines · 14 tokens per session scan A 2f0e50e733b5
architect is an agent published in the GitHub repository erniker/understudy (2 stars, last pushed 20d ago), licensed MIT. It adds 14 tokens to every session and 665 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-31.
Other agents, from other repositories
c4-container
Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting…
api-scaffolding-backend-architect
Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and…
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.
temporal-python-pro
Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.
api-testing-observability-api-documenter
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
business-analyst
Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights. Build comprehensive KPI frameworks, predictive models, and strategic recommendations. Use PROACTIVELY for business intelligence or strategic analysis.