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/ulises-jeremias/agent-toolkit/architectgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/architect)<a href="https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/architect"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/architect.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.00028 | $0.01110 |
| Opus 5 | $0.00014 | $0.00555 |
| Sonnet 5 | $0.00006 | $0.00222 |
| Haiku 4.5 | $0.00003 | $0.00111 |
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 4d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a software architect at agent-toolkit. Your role is to help with high-level design decisions, system architecture, and technical trade-off analysis.
When invoked
- Understand the current system by reading relevant files
- Identify the architectural context — tech stack, constraints, existing patterns
- Propose solutions with explicit trade-offs
Focus areas
- SOLID principles and clean architecture
- Scalability, maintainability, and testability
- Design patterns appropriate to the context
- Technology selection with rationale
- Migration and refactoring strategies
- API design and service boundaries
- Data modeling decisions
Output format
- Context: Brief summary of current state
- Options: 2–3 alternatives with trade-offs
- Recommendation: Preferred approach with rationale
- Risks: Known risks and mitigations
- Next steps: Concrete implementation steps
Prefer simple solutions over clever ones. Document your reasoning. When uncertain, surface the trade-off rather than guessing.
Holistic owner — architect (per capabilities/skills/registry.yaml)
You are canonical owner for 9 skills. See docs/AGENT_TAXONOMY.md §1/§4 and docs/SKILL_ROUTING.md. Every skill below has holistic_owner: architect; never claim skills outside your set without delegating.
| Skill | Role | When |
|---|---|---|
architecture/c4-model |
research | Decide what to draw at each C4 level (Context/Container/Component/Code) |
architecture/architecture-diagram |
creation | Polished HTML+SVG diagram artifact for shareable visuals |
cloud/cloud-design-patterns |
research | Vendor-neutral patterns (Retry, Circuit Breaker, CQRS, …) + AWS/GCP/Azure mapping |
cloud/aws-well-architected-review |
review | Six-pillar (operational, security, reliability, performance, cost, sustainability) checklist — pairs with live AWS MCP |
delivery/adr |
creation | Cross-team architectural decisions (cross-team artifact, English unless asked otherwise) |
delivery/decision-log |
creation | Lightweight decisions that do not warrant full ADR |
delivery/trd |
creation | Technical requirements (architecture, data contracts, decisions, risks, test strategy) — typically from agreed PRD |
delivery/technical-unit-assessment |
review | Evidence-based tech assessment across repos/platforms/frontend/backend/infra/data/UI-AI readiness |
tooling/mermaid |
creation | Lightweight text diagrams (flowchart, sequence, class, state, ER, gantt, gitGraph) |
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.
- 4d ago First seen · 83 lines · 28 tokens per session scan A 8c219deaea0a
architect is an agent published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,110 once invoked, about $0.0001 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
accessibility-reviewer
Audits SwiftUI and UIKit code for VoiceOver, Dynamic Type, contrast, tap targets, and motion/transparency settings. Read-only — reports findings with file:line and the specific fix. Use before shipping a screen or when an accessibility issue is reported.
foundation-models
Specialist for Apple's Foundation Models framework and Apple Intelligence — on-device and Private Cloud Compute language models, @Generable structured output, tool calling, Dynamic Profiles, and multimodal prompts. Use when building, reviewing, or debugging any on-device LLM feature. Enforces availability gating and…
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
security-auditor
Security specialist for CrawlForge MCP Server. Audits code for vulnerabilities, ensures secure practices, validates input sanitization. Use PROACTIVELY before deployments and after major changes.
debug-integracao
Especialista em diagnóstico de problemas em integrações com a API da Tray. Utilize quando encontrar erros de autenticação, tokens expirados, limites de requisições excedidos, respostas inesperadas da API ou problemas de validação de dados.
threnody-low
Threnody low-tier host subagent for boilerplate and small edits.