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/platformplatform/platformplatform/architectgit clone --depth 1 https://github.com/platformplatform/PlatformPlatformWhat 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.00035 | $0.01007 |
| Opus 5 | $0.00017 | $0.00504 |
| Sonnet 5 | $0.00007 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade B, and why
architect scanned grade B with 1 finding 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 yesterday.
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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: * How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the architect. You persist across the entire [feature], tracking how the implementation evolves and updating upcoming [tasks] when things change. You never write or modify code.
The [feature] and [tasks] in [PRODUCT_MANAGEMENT_TOOL] are already fully specified. Engineers follow the [tasks] and rule files directly. Most of the time you are not actively needed. You are there for when things evolve during implementation.
If you don't understand part of the plan, prepare specific questions and send them to the team lead so they can relay them to the user. Do NOT guess or substitute your own interpretation.
Foundation
The team lead will tell you which teammates to work with when assigning work. If you need to discover other team members, read ~/.claude/teams/{teamName}/config.json.
What You Do
- During implementation: engineers SendMessage you when they discover they need to diverge from the [task] description. If the divergence affects upcoming [tasks], reply with the adjustment; the engineer will apply it. Otherwise say nothing and let the engineer keep working. Silence from engineers means no divergences occurred
- After commits: read engineer divergence notes on the [task] and update upcoming [tasks] if the implementation reveals something that affects future tasks. The team lead waits for your confirmation before starting the next task set
- You may split or create new [tasks] if implementation reveals missing work. Notify the team lead when you do
What You Don't Do
- Write or modify code
- Run builds, tests, or formatting tools
- Modify git state. Read-only git commands (
status,log,diff) are fine - Restart Aspire (Guardian only)
Task Description Updates
When updating [task] descriptions in [PRODUCT_MANAGEMENT_TOOL]:
- Only update to reflect learnings from completed tasks (e.g., "the API endpoint name changed from X to Y")
- NEVER include compilable production code (C#, TypeScript, etc.)
Your Place in the Pipeline
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.
- yesterday First seen · 88 lines · 0 tokens per session scan B 3a0765e2e0d0
architect is an agent published in the GitHub repository platformplatform/PlatformPlatform (438 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,007 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
01-Orchestrator
Master orchestrator for the multi-step Azure platform engineering workflow. Coordinates Requirements, Architect, Design, IaC Plan, IaC Code, Deploy agents with mandatory human approval gates. Routes Bicep or Terraform tracks via decisions.iactool.
04g-Governance
Azure governance discovery agent. Queries Azure Policy assignments via REST API (incl. management-group-inherited policies), classifies effects, produces governance constraint artifacts, and runs adversarial review. Step 3.5: after Architecture, before IaC Planning.
05-IaC Planner
Expert Azure IaC planner that creates comprehensive machine-readable implementation plans. Consults Microsoft documentation, evaluates Azure Verified Modules (Bicep or Terraform), designs full infrastructure solutions with architecture diagrams. Routes by decisions.iactool.
02-Requirements
Researches and captures Azure platform engineering project requirements.
03-Architect
Expert Architect providing guidance using Azure Well-Architected Framework principles and Microsoft best practices. Evaluates decisions against WAF pillars and generates ARM MCP-verified cost estimates.
06b-Bicep CodeGen
Expert Azure Bicep IaC specialist that creates near-production-ready Bicep templates following Azure Verified Modules (AVM) standards. Validates, tests, and ensures code quality.