MultiClaude: Command for Claude Code

.claude/commands/ipa/detail.md

detail is a command for Claude Code from nguyennguyenit/MultiClaude. It costs 16 tokens per session (579 once invoked), scanned A, original, MIT.

A command that creates detailed API and database design documents from the project's earlier requirements and interface documents. An API is the defined way software components exchange data, while a database schema describes stored data and its relationships.

In plain words
What is it for?
Use it to generate `docs/API_SPEC.md` and `docs/DB_DESIGN.md`, define API requests and responses, design tables and relationships, and include a Mermaid entity-relationship diagram.
Why use it?
It connects the requested features and screens to the backend endpoints and database tables needed to implement them. It also checks that earlier design files exist before producing detailed designs.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

This is nguyennguyenit/MultiClaude's own configuration. It tells Claude Code how to work on MultiClaude itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything MultiClaude configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/nguyennguyenit/MultiClaude/master/.claude/commands/ipa/detail.md
Clone the repo
git clone --depth 1 https://github.com/nguyennguyenit/MultiClaude

Made for: Claude Code.

Wrote 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.

agentmods badge for detail

README.md
[![agentmods](https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/detail/github.svg)](https://agentmods.dev/commands/nguyennguyenit/multiclaude/detail)
Your own site
<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/detail"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/detail/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for detail

Your own site · 80×15
<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/detail"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/detail.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 579 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00579
Opus 5 $0.00008 $0.00290
Sonnet 5 $0.00003 $0.00116
Haiku 4.5 $0.00002 $0.00058

Measured 9d ago against content hash b0fe694243a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

detail 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 9d 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.

.claude/commands/ipa/detail.md · 91 lines

What it actually says

You are an expert Systems Architect specializing in IPA (Japan Standard) detailed design.

Objective

Generate Stage 3 documents:

  1. docs/API_SPEC.md (Detailed API Design)
  2. docs/DB_DESIGN.md (Database Schema Design)

Prerequisites

Check that Stage 1 and 2 are complete:

  • docs/SRD.md MUST exist
  • docs/UI_SPEC.md MUST exist
  • prototypes/html-mockups/ SHOULD exist (warn if not)

Workflow

  1. Analyze Requirements:

    • Read SRD.md (get FR-xx, S-xx, E-xx)
    • Read UI_SPEC.md (understand data needs for screens)
    • Read html-mockups (visualize data flow)
  2. Generate DB_DESIGN.md:

    • Design schema based on Entity List (E-xx)
    • Define tables, columns, types, relationships
    • Ensure 3NF (Third Normal Form)
    • Include ER Diagram (Mermaid)
  3. Generate API_SPEC.md:

    • Design API endpoints to support Screens (S-xx) and Features (FR-xx)
    • Define: Method, URL, Request/Response schemas
    • Ensure every FR-xx and S-xx is supported by an API

Required Output Structure

1. docs/DB_DESIGN.md

# Database Detailed Design

## 1. ER Diagram
[Mermaid ERD]

## 2. Table Definitions

### E-01: Users (users)
| Column | Type | Constraints | Description |
|--------|------|-------------|-------------|
| id | uuid | PK | Unique ID |
| email | varchar | Unique, Not Null | User email |

2. docs/API_SPEC.md

# Interface Specification (API)

## 1. Endpoint Matrix
| Method | URL | Feature (FR-xx) | Screen (S-xx) |
|--------|-----|-----------------|---------------|
| POST | /auth/login | FR-01 | S-01 |

## 2. Endpoint Details

### POST /auth/login
- **Description**: Authenticate user
- **Request**:
  ```json
  { "email": "...", "password": "..." }
  • Response:
    { "token": "..." }
    

## Traceability Check

Ensure:
- Every Table corresponds to an E-xx
- Every Endpoint links to an FR-xx

## Next Steps

**Next:** `/plan` to generate implementation tasks
Changes

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.

  1. 9d ago First seen · 91 lines · 0 tokens per session scan A b0fe694243a8

Subscribe to this mod's changes

detail is a command published in the GitHub repository nguyennguyenit/MultiClaude (22 stars, last pushed 28d ago), licensed MIT. It adds 16 tokens to every session and 579 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.