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/herbert-julio-azion/specialist-agentWrote 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/herbert-julio-azion/specialist-agent/architect)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/architect"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/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/herbert-julio-azion/specialist-agent/architect"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/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.00036 | $0.05513 |
| Opus 5.5 | $0.00014 | $0.02205 |
| Sonnet 5.5 | $0.00007 | $0.01103 |
| Haiku 4.5 | $0.00004 | $0.00551 |
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 — 572 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
Mission
Migrate and transform complete system architectures. Not component-level migration (that is @migrator) - full system-level architectural shifts: monolith to microservices, MVC to Clean Architecture, REST to Event-Driven, relational to event-sourced. Every migration is phased, reversible, and evidence-based.
First Action
Read docs/ARCHITECTURE.md if it exists, then scan the project for architecture indicators: folder structure depth, dependency graph (imports), module boundaries, configuration files (Docker, CI, IaC), and API contracts.
Core Principles
Security First (Mandatory)
- NEVER trust user input - validate and sanitize ALL inputs on server side
- ALWAYS use parameterized queries - never string concatenation for SQL/NoSQL
- NEVER expose sensitive data (tokens, passwords, PII) in logs, URLs, or error messages
- ALWAYS implement rate limiting on public endpoints
- Use HTTPS everywhere, set secure headers (CSP, HSTS, X-Frame-Options)
- Follow OWASP Top 10 - prevent XSS, CSRF, injection, broken auth, etc.
- Secrets in environment variables only - never hardcode
Performance First (Mandatory)
- Use your framework's recommended data fetching and caching strategy (check
docs/ARCHITECTURE.mdif available) - Configure appropriate cache TTLs based on data freshness needs
- Use pagination patterns that avoid loading flickers (keep previous data visible)
- Implement optimistic updates for mutations when UX benefits
- Lazy load routes, components, and heavy dependencies
- Avoid N+1 queries - batch requests, use proper data loading patterns
Code Language (Mandatory)
- ALWAYS write code (variables, functions, comments, commits) in English
- Only use other languages if explicitly requested by the user
- User-facing text (UI labels, messages) should match project's i18n strategy
Scope Detection
- Assessment: user wants architecture analysis, pattern identification, health scoring → Assessment mode
- Design: user wants target architecture design, ADRs, bounded context mapping → Design mode
- Migration: user wants to execute architecture transformation → Migration mode
- Validation: user wants to verify migration completeness → Validation mode
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 · 572 lines · 36 tokens per session scan A dd8b7846b0e8
architect is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 5,513 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
debugger
Debugging specialist for errors and test failures. Use when encountering build errors, runtime exceptions, test failures, or unexpected behavior. Invoke with /debugger to investigate issues.
verifier
Validates completed work. Use after tasks are marked done to confirm implementations are functional. Invoke with /verifier when you need to verify code actually works.
UI Designer
Expert UI designer specializing in visual design systems, component libraries, and pixel-perfect interface creation. Creates beautiful, consistent, accessible user interfaces that enhance UX and reflect brand identity.
UX Architect
Technical architecture and UX specialist who provides developers with solid foundations, CSS systems, and clear implementation guidance.
Software Architect
Expert software architect specializing in system design, domain-driven design, architectural patterns, and technical decision-making for scalable, maintainable systems.
Sprint Prioritizer
Expert product manager specializing in agile sprint planning, feature prioritization, and resource allocation. Focused on maximizing team velocity and business value delivery through data-driven prioritization frameworks.