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/syncgit 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/sync)<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/sync"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/sync.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.00017 | $0.00624 |
| Opus 5 | $0.00009 | $0.00312 |
| Sonnet 5 | $0.00003 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
sync 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 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.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Sync IPA-generated documentation with actual implementation after /code completion.
Docs to Sync
| Doc | Sync From | When |
|---|---|---|
docs/API_SPEC.md |
Actual API endpoints in codebase | After BE tasks |
docs/DB_DESIGN.md |
Actual database schema | After BE tasks |
docs/UI_SPEC.md |
Actual UI components | After FE tasks (if changed) |
Workflow
Step 1: Detect Changes
- Read current
docs/API_SPEC.md - Scan codebase for actual API endpoints:
- Look for route definitions (Express, NestJS, FastAPI, etc.)
- Extract request/response types
- Compare and identify differences
Step 2: Update API_SPEC.md
If differences found:
- Update endpoint list
- Update request/response schemas
- Update error codes
- Update Endpoint Matrix Status column:
- ⏳ → ✅ (when endpoint is implemented)
- ✅ → 🔄 (when docs match code exactly)
- Preserve manual notes/comments
Step 3: Update DB_DESIGN.md
- Read actual database schema (Drizzle, Prisma, TypeORM, etc.)
- Compare with
docs/DB_DESIGN.md - Update:
- Table definitions
- Column types
- Relationships
- Indexes
Step 4: Update UI_SPEC.md (if requested)
Only if $ARGUMENTS contains "ui" or "all":
- Scan UI components
- Update screen list
- Update component specs
Usage
# Sync API and DB docs (default after BE)
/docs:sync
# Sync all including UI
/docs:sync all
# Sync specific doc
/docs:sync api
/docs:sync db
/docs:sync ui
Output
Report changes made:
## Docs Sync Report
### API_SPEC.md
- Added: POST /api/users/register
- Updated: GET /api/users/:id response schema
- Removed: (none)
- **Status Updates:**
- POST /auth/login: ⏳ → ✅
- POST /auth/register: ⏳ → ✅
- GET /users/:id: ⏳ → 🔄 (synced)
### DB_DESIGN.md
- Added: sessions table
- Updated: users table (added email_verified column)
- Removed: (none)
### UI_SPEC.md
- (not synced - use /docs:sync ui)
Important
- Preserve manual notes: Don't overwrite human-added comments
- Backup before sync: Create backup if significant changes
- Review changes: Show diff before applying
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 · 111 lines · 17 tokens per session scan A 575cb3e84d07
sync is a command published in the GitHub repository nguyennguyenit/MultiClaude (22 stars, last pushed 23d ago), licensed MIT. It adds 17 tokens to every session and 624 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.