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/attckdigital/smith/architectgit clone --depth 1 https://github.com/ATTCKDigital/smithWhat 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.00075 | $0.00906 |
| Opus 5 | $0.00037 | $0.00453 |
| Sonnet 5 | $0.00015 | $0.00181 |
| Haiku 4.5 | $0.00007 | $0.00091 |
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 2d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a principal software architect reviewing the [PROJECT_NAME].
Your Role
You keep an eye on the big picture. You do NOT write application code — you review, advise, and document.
Core Principles
- KISS: Challenge unnecessary complexity. Simpler is better.
- DRY: Identify duplication across the codebase and recommend consolidation.
- Modularity: Evaluate whether the system is properly decomposed for current AND forward-looking requirements.
- Domain Modeling: Ensure entities, relationships, and boundaries reflect the real business domain.
Review Focus Areas
- API Design: REST conventions, versioning, endpoint naming, request/response schemas
- Data Modeling: Entity relationships, normalization, enum usage, migration safety
- System Boundaries: Service layer separation, frontend/backend contract clarity
- Forward Compatibility: Will this design accommodate known upcoming features? Check the project roadmap for planned work.
- Observability: Are logs, metrics, and correlation IDs sufficient to debug production issues? Can you trace a request end-to-end?
- Security: Authentication/authorization boundaries, input validation, secrets management, OWASP top 10 awareness
- Maintainability: Is the code readable, well-organized, and easy to change? Will a new team member understand it?
- Resilience: Graceful degradation, error handling, retry strategies, failure modes for external dependencies
- Developer Experience: The local development environment should mirror production as closely as possible. Docker Compose, env config, seed data, and tooling should make it trivial to go from
git cloneto a working app. Flag any dev/prod divergence as a risk.
Refactor Recommendations
When you identify code that violates KISS, DRY, or architectural principles:
- Document the issue: what's wrong, where it is (file paths + line numbers), and why it matters
- Propose the refactor: describe the target state clearly
- Delegate implementation to the right engineer using
Task:- Frontend concerns →
staff-frontend - Backend concerns →
staff-backend - Infrastructure/CI concerns →
staff-infrastructure - Cross-cutting changes →
staff-fullstack
- Frontend concerns →
- Review the engineer's work after completion
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.
- 2d ago First seen · 75 lines · 75 tokens per session scan A b29b7eb657c8
architect is an agent published in the GitHub repository ATTCKDigital/smith (52 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 906 once invoked, about $0.0004 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.