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 skills/p47phoenix/claude-plugins/architectnpx skills add P47Phoenix/Claude-Plugins --skill architectgit clone --depth 1 https://github.com/P47Phoenix/Claude-PluginsWhat 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.00120 | $0.03780 |
| Opus 5 | $0.00060 | $0.01890 |
| Sonnet 5 | $0.00024 | $0.00756 |
| Haiku 4.5 | $0.00012 | $0.00378 |
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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
Design Principle: Role Context Isolation
Architecture-specific knowledge stays out of the main context window. Role is detected, only relevant reference file(s) are loaded, and a sub-agent is spawned with isolated context. Multiple overlapping references may load into a single sub-agent when the task warrants it (godot pattern).
Phase 1: Role Detection
Detect the relevant architect role(s) from (in priority order):
- Explicit role mention — "as a solution architect", "enterprise architecture perspective", "game systems architecture"
- Task type signals — see routing tables below
- Domain signals — game-related keywords (ECS, netcode, render pipeline, LOD, navmesh) route to game roles; business/enterprise keywords (TOGAF, capability map, microservices, API gateway) route to software roles
- Scope signals — single system/feature → Solution; cross-system/portfolio → Enterprise; data-centric → Data; security-centric → Security
If ambiguous, ask before proceeding. Do not assume.
Declare before every task:
Role: [ROLE] | Task: [TYPE] | Model: [recommended_model] | References: [list of reference files]
Model Split (W2-6)
Skill router MUST return {role, task_type, recommended_model} to the orchestrator.
| Phase | recommended_model | task_types |
|---|---|---|
| Classification | sonnet |
Prior Art Analysis, paradigm pick, decomposition pick, compliance-checklist, privacy-assessment, incident-response-plan, review, game-review |
| Synthesis | opus |
design, document, game-design-doc, transformation-planning, evaluate, data-design, security-design, strategic, integration |
| Checklist/Policy | sonnet |
security-requirements, audit-preparation, risk-assessment, policy-document, analyze-quality, model |
Orchestrator may override via architecture.model_override in .delivery/config.yml.
Prior Art Analysis
What ships with it
51 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- paradigms/ddd/references/strategic-ddd.md 16 KB
- paradigms/ddd/SKILL.md 3.7 KB
- paradigms/volatility/references/domain-discovery-volatility.md 2.5 KB
- paradigms/volatility/references/volatility-decomposition.md 15 KB
- paradigms/volatility/SKILL.md 3.1 KB
- references/adr-lifecycle.md 6.4 KB
- references/adr-template.md 12 KB
- references/architecture-patterns.md 9.9 KB
- references/c4-model.md 11 KB
- references/compliance-frameworks.md 8.2 KB
- references/contracts/cross-role-tasks.md 2.7 KB
- references/data-modeling.md 12 KB
- references/decomposition/architecture-style.md 5.2 KB
- references/domain-discovery.md 11 KB
- references/enterprise-patterns.md 9.9 KB
- references/event-storming.md 6.6 KB
- references/game-systems.md 13 KB
- references/graphics-rendering.md 18 KB
- references/guardrails.md 2.7 KB
- references/incident-response.md 11 KB
- references/level-world.md 14 KB
- references/network-multiplayer.md 14 KB
- references/output-contracts/adr.md 537 B
- references/output-contracts/design.md 976 B
- references/output-contracts/evaluation.md 589 B
- references/output-contracts/game.md 1.0 KB
- references/output-contracts/review.md 609 B
- references/privacy-patterns.md 13 KB
- references/quality-attributes.md 15 KB
- references/roles/compliance.md 2.4 KB
- references/roles/data.md 1.1 KB
- references/roles/enterprise.md 1.6 KB
- references/roles/game-systems.md 1.8 KB
- references/roles/graphics-rendering.md 1.6 KB
- references/roles/incident-responder.md 1.2 KB
- references/roles/level-world.md 1.6 KB
- references/roles/network-multiplayer.md 1.7 KB
- references/roles/privacy.md 1.7 KB
- references/roles/security.md 2.2 KB
- references/roles/solution.md 3.9 KB
- references/security-patterns.md 14 KB
- references/security-requirements.md 9.6 KB
- references/strategic-ddd.md 505 B
- references/team-topology.md 6.5 KB
- references/technology-evaluation.md 15 KB
- references/transformation-phase-1a-behavioral.md 7.0 KB
- references/transformation-phase-1b-structural.md 4.7 KB
- references/transformation-phase-2-to-be.md 5.3 KB
- references/transformation-phase-3-roadmap.md 6.9 KB
- references/transformation-planning.md 6.4 KB
- references/volatility-decomposition.md 502 B
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 · 295 lines · 120 tokens per session scan A e76dd5a546eb
architect is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 120 tokens to every session and 3,780 once invoked, about $0.0006 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…