Borrowing it
Nothing to install: this file belongs to nguyennguyenit/MultiClaude. 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/nguyennguyenit/MultiClaude/master/.claude/commands/ipa/all.mdgit clone --depth 1 https://github.com/nguyennguyenit/MultiClaudeWrote 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/nguyennguyenit/multiclaude/all)<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/all"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/all.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.00016 | $0.00812 |
| Opus 5 | $0.00008 | $0.00406 |
| Sonnet 5 | $0.00003 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
all 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ DEPRECATION WARNING
This command skips validation gates (GATE 1/2/3).
Recommended flow:
/lean → /ipa:spec → /ipa:design → /ipa:detailUse
/ipa:allonly for:
- Rapid prototyping (throwaway code)
- Existing projects with established docs
- Power users who understand the risks
Purpose
Generate all IPA documentation in sequence:
- SRD (System Requirement Definition)
- BD (Basic Design / UI_SPEC)
- DD (Detail Design / API_SPEC + DB_DESIGN)
Input
If empty, look for:
docs/requirements.mddocs/PRD.md- Ask user for requirements
Workflow
Step 1: Generate SRD
Execute /ipa:srd logic:
- Read requirements
- Generate
docs/SRD.mdwith 14 IPA sections - Ask user to review
Wait for user approval before continuing.
Step 2: Generate Basic Design
Execute /ipa:bd logic:
- Read
docs/SRD.md - Generate
docs/UI_SPEC.md - Optionally generate
ui-mockup/*.html - Ask user to review
Wait for user approval before continuing.
Step 3: Generate Detail Design
Execute /ipa:dd logic:
- Read
docs/SRD.md+docs/UI_SPEC.md - Generate
docs/API_SPEC.md - Generate
docs/DB_DESIGN.md - Ask user to review
Wait for user approval before continuing.
Step 4: Auto-Validate (Built-in)
Execute /ipa:validate logic automatically:
- Check ID consistency (FR-xx, S-xx, E-xx)
- Validate traceability chain
- Check cross-references
- Report any errors/warnings
✓ Validation Summary:
- Features (FR): 10 ✓
- Screens (S): 8 ✓
- Entities (E): 6 ✓
- Errors: 0
- Warnings: 2 (orphan IDs)
- Status: PASS
If errors found, prompt user to fix before proceeding.
Output Summary
After completion:
docs/
├── SRD.md # System Requirement Definition
├── UI_SPEC.md # Basic Design (screens)
├── API_SPEC.md # Detail Design (API)
├── DB_DESIGN.md # Detail Design (DB)
└── tech-stack.md # (if created)
ui-mockup/ # (optional)
├── login.html
├── dashboard.html
└── ...
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 · 152 lines · 16 tokens per session scan A 41368637b99e
all is a command published in the GitHub repository nguyennguyenit/MultiClaude (22 stars, last pushed 26d ago), licensed MIT. It adds 16 tokens to every session and 812 once invoked, about $0.0001 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 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.