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 commands/nguyennguyenit/multiclaude/ddgit 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/dd)<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/dd"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/dd.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.05122 |
| Opus 5 | $0.00009 | $0.02561 |
| Sonnet 5 | $0.00003 | $0.01024 |
| Haiku 4.5 | $0.00002 | $0.00512 |
Grade A, and why
dd 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 — 835 lines — stays where its author put it; the contents beside it link to each section on GitHub.
💡 TIP:
/ipa:detailis the new canonical name for this command.Both commands produce the same output.
/ipa:ddis kept for backward compatibility.
Purpose
Generate Detail Design (内部設計) following IPA standard. Platform Agnostic - works with any project type.
Output:
docs/INTERFACE_SPEC.md- Interface specifications (API/CLI/MCP/Chat)docs/DB_DESIGN.md- Data design (SQL/NoSQL/Vector/File)
Project Type Detection
| Project Type | Interface Spec | Data Design |
|---|---|---|
| Web App | REST/GraphQL API | SQL/NoSQL |
| Desktop App | IPC/Native API | SQLite/Local |
| CLI Tool | Commands/Args/Flags | Config files |
| MCP Server | Tools/Resources/Prompts | - |
| Chatbot/RAG | Conversation flows | Vector DB |
| Library/SDK | Public API/Methods | - |
Input
Required:
docs/SRD.mddocs/UI_SPEC.md
Optional:
docs/tech-stack.md(for implementation hints only, not required)
Language-Agnostic Principle
┌─────────────────────────────────────────────────────────────────────┐
│ LANGUAGE-AGNOSTIC DESIGN │
├─────────────────────────────────────────────────────────────────────┤
│ │
│ API_SPEC.md uses: │
│ - OpenAPI 3.x standard (YAML/JSON) │
│ - Standard HTTP methods (GET, POST, PUT, DELETE) │
│ - JSON Schema for request/response │
│ - NO framework-specific code │
│ │
│ DB_DESIGN.md uses: │
│ - Standard SQL (DDL) │
│ - ER Diagram (Mermaid) │
│ - Portable data types │
│ - NO ORM-specific syntax │
│ │
│ Implementation notes (optional): │
│ - If tech-stack.md exists, add hints for that stack │
│ - Hints are in separate "Implementation Notes" section │
│ │
└─────────────────────────────────────────────────────────────────────┘
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 · 835 lines · 17 tokens per session scan A 286ec1975dc3
dd 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 5,122 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
review-renovate
Review and merge renovate PRs with automerge configuration updates.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
plan-regression-tests
Plan regression tests for existing code with it.skip statements.
init
Initialize configurations for Supabase local development.
volume-admin-set-status
Changes the operational status of a named volume.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.