Borrowing it
Nothing to install: this file belongs to Burly-Mingo/modernization-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Burly-Mingo/modernization-kit/main/.claude/commands/phase-3-target-architecture.mdgit clone --depth 1 https://github.com/Burly-Mingo/modernization-kitWrote 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/commands/burly-mingo/modernization-kit/phase-3-target-architecture)<a href="https://agentmods.dev/commands/burly-mingo/modernization-kit/phase-3-target-architecture"><img src="https://agentmods.dev/badge/commands/burly-mingo/modernization-kit/phase-3-target-architecture.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.1 | $0.00000 | $0.00576 |
| Opus 5 | $0.00000 | $0.00288 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
phase-3-target-architecture 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 7d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 3: Target Architecture Design
Propose the future-state architecture based on Phases 0-2. Expect multiple revision cycles.
Before Designing: Rationalize the Landscape
- Should these remain separate applications, or should some be consolidated?
- Should any applications or features be retired entirely?
- Are there workflows that exist because of old technical limitations?
- Do current app boundaries match how the business actually works today?
- Document the rationalized view — what the org actually needs vs. what it has.
Architecture Areas
1. Application Architecture: Monolith, modular monolith, or microservices (justify). Module boundaries mapped to business domains. Communication patterns.
2. Frontend Strategy: Rendering strategy (SPA, SSR, SSG, hybrid). Framework recommendation. Mobile strategy. Accessibility. For public-facing apps: SEO and AI discoverability drive the tech stack — a site dependent on search traffic cannot be a client-only SPA.
3. Backend Strategy: Language/framework. API design. Background jobs. Real-time communication. File storage.
4. Data Architecture: Database tech. Schema design. Data access strategy (and WHY). Caching. Search. Data migration approach.
5. Auth & Authorization: Identity provider (buy vs. build). Role/permission model. SSO/federation. API auth.
6. Infrastructure & Deployment: Container orchestration. CI/CD. Environments. Monitoring/logging/alerting. Secrets management. Edge security.
7. AI/ML Integration: Tasks AI could improve. On-prem vs. cloud. Model selection. Inference infrastructure.
8. Modern Capabilities Scan: Problem-first check — caching, real-time, messaging, API management, search, AI/ML, MCP/agents, workflow orchestration. For each: pain point it solves, impact, effort, red team critique. If it doesn't trace to a real problem, discard it.
9. DR & Business Continuity: RPO/RTO. Backup. Failover. Geographic risk.
10. Buy vs. Build: For every component that could be purchased.
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.
- 7d ago First seen · 50 lines · 0 tokens per session scan A 6fbe03eb60f4
phase-3-target-architecture is a command published in the GitHub repository Burly-Mingo/modernization-kit (11 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 576 tokens. 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 commands, from other repositories
ask
⚡ Answer technical and architectural questions.
use-mcp
Utilize tools of Model Context Protocol (MCP) servers.
cook
⚡⚡⚡ Implement a feature [step by step].
code
⚡ Start coding & testing an existing plan.
plan
⚡⚡⚡ Intelligent plan creation with prompt enhancement.
bootstrap
Bootstrap the project from scratch with dependencies and configuration.