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/splitgit 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/split)<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/split"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/split.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 | $0.00008 | $0.00826 |
| Opus 5 | $0.00004 | $0.00413 |
| Sonnet 5 | $0.00002 | $0.00165 |
| Haiku 4.5 | $0.00001 | $0.00083 |
Grade C, and why
split scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf docs/API_SPEC/ How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Split large IPA documentation files (API_SPEC, DB_DESIGN, SRD) into modular folder structure when files exceed 500 lines.
Usage
# Split specific doc
/ipa-docs:split API_SPEC
/ipa-docs:split DB_DESIGN
/ipa-docs:split SRD
# Auto-detect and split all large docs
/ipa-docs:split
Output Structure
Before (Single File)
docs/
├── API_SPEC.md # 800+ lines, hard to navigate
After (Modular)
docs/
├── API_SPEC/
│ ├── README.md # Agent guide for this folder
│ ├── index.md # Endpoint matrix (mục lục)
│ ├── auth.md # /auth/* endpoints
│ ├── users.md # /users/* endpoints
│ └── orders.md # /orders/* endpoints
Workflow
Step 1: Analyze Document
- Read target doc (e.g.,
docs/API_SPEC.md) - Check line count:
- < 500 lines: Skip (no split needed)
- ≥ 500 lines: Proceed with split
- Identify sections by headers (## or ###)
Step 2: Create Folder Structure
- Create folder:
docs/{DOC_NAME}/ - Generate
README.md:
# {DOC_NAME}
This folder contains modular IPA documentation split from {DOC_NAME}.md
## Files
| File | Description |
|------|-------------|
| index.md | Overview and navigation |
| {section}.md | {Section description} |
## Usage
Agent should read `index.md` first for overview, then specific files as needed.
Step 3: Generate index.md
Extract matrix/overview section:
- For API_SPEC: Endpoint Matrix table
- For DB_DESIGN: Table Matrix
- For SRD: Requirements Matrix (FR-xx list)
Add links to detail files.
Step 4: Split Content
For each major section (identified by ## headers):
- Create
{section-slug}.md - Move section content
- Add backlink to index.md
Section Detection by Doc Type
API_SPEC.md
Split by API group:
- Sections with
/auth/*→auth.md - Sections with
/users/*→users.md - Sections with
/orders/*→orders.md
DB_DESIGN.md
Split by domain:
- User tables →
users-tables.md - Order tables →
orders-tables.md - System tables →
system-tables.md
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.
- 4d ago First seen · 149 lines · 8 tokens per session scan C 817fb6fb852d
split is a command published in the GitHub repository nguyennguyenit/MultiClaude (22 stars, last pushed 23d ago), licensed MIT. It adds 8 tokens to every session and 826 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
document
Document a file or directory comprehensively - shaking the tree to truly understand it.
brand-generate
Generate an on-brand document from a saved Brand Profile.
tree
Show file tree with sync status indicators showing which files are indexed, modified, new, or deleted.
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.