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/bd.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/bd)<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/bd"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/bd.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.00017 | $0.02597 |
| Opus 5 | $0.00009 | $0.01299 |
| Sonnet 5 | $0.00003 | $0.00519 |
| Haiku 4.5 | $0.00002 | $0.00260 |
Grade A, and why
bd 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 6d 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
💡 TIP: Use
/ipa:specinstead to generate both SRD.md + UI_SPEC.md in one step.This command is kept for granular control when you only need UI_SPEC.md.
Prerequisite:
docs/SRD.mdmust exist.
Purpose
Generate Basic Design (外部設計) following IPA standard with:
- Customer Journey Experience (CJX)
- Design reference support (URL/image)
- Platform-specific UX patterns
Output: docs/UX_SPEC.md
Project Type Detection
| Project Type | UX Spec Focus | CJX Adaptation |
|---|---|---|
| Web App | Screens, components, responsive | Visual journey |
| Desktop App | Windows, dialogs, menus | Productivity journey |
| CLI Tool | Commands, output, prompts | Task completion journey |
| MCP Server | Tool descriptions, prompts | Developer journey |
| Chatbot/RAG | Conversation flows, responses | Query resolution journey |
| Library/SDK | API docs, examples | Integration journey |
Input
Required:
docs/SRD.md
Optional:
$ARGUMENTS= Reference URL or image path for design inspirationdocs/tech-stack.md
User Research Integration
Before starting UI design, check for USER_RESEARCH.md:
if docs/USER_RESEARCH.md exists:
1. Read personas and journey maps
2. Map journey stages to screens
3. Add "Design Rationale" to each screen
4. Apply emotional design (CJX)
else:
Proceed with UI design (without rationale)
For each screen, add Design Rationale section:
### S-XX: [Screen Name]
**Journey Stage:** [Discovery/Onboarding/Usage/Retention/Advocacy]
**User Emotion:** [From journey map]
**Persona:** [Which persona uses this screen]
**Design Rationale:**
- Decision 1: [Why] (addresses [pain point/goal from persona])
- Decision 2: [Why]
[Rest of screen spec...]
Example:
### S-02: Dashboard
**Journey Stage:** Usage (Engaged → Productive)
**User Emotion:** Focused, wants efficiency
**Persona:** Sarah (SaaS PM)
**Design Rationale:**
- Quick actions prominent: Sarah values speed (persona behavior)
- Data visualization: Sarah is data-driven, needs metrics at a glance
- Minimal navigation: Reduce tool-switching overhead (persona pain point)
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.
- 6d ago First seen · 394 lines · 17 tokens per session scan A 3bc98e9cd734
bd is a command published in the GitHub repository nguyennguyenit/MultiClaude (22 stars, last pushed 25d ago), licensed MIT. It adds 17 tokens to every session and 2,597 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
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
team-ui
Orchestrate UI/UX design team.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.