Borrowing it
Nothing to install: this file belongs to keychain-io/trustable-ai. 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/keychain-io/trustable-ai/main/.claude/commands/architecture-planning.mdgit clone --depth 1 https://github.com/keychain-io/trustable-aiWrote 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/keychain-io/trustable-ai/architecture-planning)<a href="https://agentmods.dev/commands/keychain-io/trustable-ai/architecture-planning"><img src="https://agentmods.dev/badge/commands/keychain-io/trustable-ai/architecture-planning.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.03427 |
| Opus 5 | $0.00000 | $0.01714 |
| Sonnet 5 | $0.00000 | $0.00685 |
| Haiku 4.5 | $0.00000 | $0.00343 |
Grade A, and why
architecture-planning 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 8d 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 — 536 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Planning Workflow
Project: trusted-ai-development-workbench Workflow: Architecture Planning Purpose: Design technical architecture, validate technology choices, and document system design
Output Formatting Requirements
IMPORTANT: Use actual Unicode emojis in reports, NOT GitHub-style shortcodes.
Where This Fits
┌─────────────────────────────────────────────────────────────────────────────┐
│ SOFTWARE LIFECYCLE - ARCHITECTURE PHASE │
│ │
│ /product-intake │
│ │ Creates Epics and Features from requirements │
│ ▼ │
│ ══════════════════ │
│ YOU ARE HERE: /architecture-planning │
│ ══════════════════ │
│ │ Input: Feature requirements, tech constraints │
│ │ Output: Architecture docs in docs/architecture/ │
│ ▼ │
│ /backlog-grooming │
│ │ Breaks Features into Tasks with architecture context │
│ ▼ │
│ /sprint-planning │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
Prerequisites
Before running this workflow, you need:
- Feature Requirements:
- Features from /product-intake or existing backlog
- Acceptance criteria defined
- Business context understood
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.
- 8d ago First seen · 536 lines · 0 tokens per session scan A 0e5f0aa648b2
architecture-planning is a command published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,427 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.