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/importgit 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/import)<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/import"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/import.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.00010 | $0.01168 |
| Opus 5 | $0.00005 | $0.00584 |
| Sonnet 5 | $0.00002 | $0.00234 |
| Haiku 4.5 | $0.00001 | $0.00117 |
Grade A, and why
import 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Import external requirements documents (from Gemini Deep Research, Perplexity, manual SRS) into IPA documentation structure with proper IDs and traceability.
Usage
# Import from markdown file
/ipa:import @path/to/external-srs.md
# Import from PDF (uses AI vision)
/ipa:import @path/to/requirements.pdf
# Import with specific focus
/ipa:import @external.md --focus=api # Only API requirements
/ipa:import @external.md --focus=ui # Only UI requirements
Workflow
Step 1: Read External Document
- Read external SRS file (md/pdf)
- Analyze structure and identify sections:
- Business requirements
- Functional requirements
- UI/UX specifications
- API requirements
- Data/Database requirements
- Non-functional requirements
Step 2: Extract and Categorize
Map external content to IPA docs:
| External Content | → | IPA Doc |
|---|---|---|
| Business requirements | → | SRD.md (FR-xx) |
| User stories | → | SRD.md (FR-xx) |
| UI mockup descriptions | → | UI_SPEC.md (S-xx) |
| Screen flows | → | UI_SPEC.md (flows) |
| API endpoints | → | API_SPEC.md (API-xx) |
| Data models | → | DB_DESIGN.md (D-xx) |
| ERD descriptions | → | DB_DESIGN.md |
Step 3: Generate IPA IDs
Assign IPA-compliant IDs:
| Type | ID Format | Example |
|---|---|---|
| Functional Requirement | FR-XXX | FR-001, FR-002 |
| Screen | S-XX | S-01, S-02 |
| Entity | E-XX | E-01, E-02 |
| API Endpoint | API-XXX | API-001, API-002 |
| Database Table | D-XX | D-01, D-02 |
Step 4: Generate IPA Docs
Create/update IPA docs:
/ipa:import @external-srs.md
↓
docs/
├── SRD.md # Generated with FR-xx IDs
├── UI_SPEC.md # Generated with S-xx IDs
├── API_SPEC.md # Generated with API-xx IDs
└── DB_DESIGN.md # Generated with D-xx IDs
Step 5: Validate
Run /ipa:validate automatically to check:
- ID uniqueness
- Traceability links
- Required fields
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 · 198 lines · 10 tokens per session scan A 6b7395fbaa34
import is a command published in the GitHub repository nguyennguyenit/MultiClaude (22 stars, last pushed 25d ago), licensed MIT. It adds 10 tokens to every session and 1,168 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
organize-files
Organize and rename files based on content analysis.
tree
Show file tree with sync status indicators showing which files are indexed, modified, new, or deleted.
prose-review-docs
Reviews markdown documentation files or directories against the active prose style rules — the plugin's vendor-neutral baseline plus your organization's overlay when one is configured. Accepts a file path or directory (recursive). Runs prose-style-checker and optionally Vale. Supports --fix to auto-apply safe…
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
convert
Convert a file to Markdown using markitdown.