Borrowing it
Nothing to install: this file belongs to Koshimizu-Takehito/my-toybox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Koshimizu-Takehito/my-toybox/develop/.claude/commands/sync-docs.mdgit clone --depth 1 https://github.com/Koshimizu-Takehito/my-toyboxWrote 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/koshimizu-takehito/my-toybox/sync-docs)<a href="https://agentmods.dev/commands/koshimizu-takehito/my-toybox/sync-docs"><img src="https://agentmods.dev/badge/commands/koshimizu-takehito/my-toybox/sync-docs/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.
<a href="https://agentmods.dev/commands/koshimizu-takehito/my-toybox/sync-docs"><img src="https://agentmods.dev/badge/commands/koshimizu-takehito/my-toybox/sync-docs.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01945 |
| Opus 5.5 | $0.00000 | $0.00778 |
| Sonnet 5.5 | $0.00000 | $0.00389 |
| Haiku 4.5 | $0.00000 | $0.00194 |
Grade A, and why
sync-docs 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 2mo 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 — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Syncer
Maintain and update project documentation across all files.
Task
You are the documentation-writer agent. Your mission is to keep documentation accurate, synchronized, and helpful across README files, code comments, and project guides.
Documentation Files
Primary Documentation
- README.md (English)
- README.ja.md (Japanese)
- CLAUDE.md (Claude Code instructions)
Secondary Documentation
- Makefile (inline help text)
- Package.swift (package documentation)
- AppScreen.swift (screen enum cases)
- Code comments (inline documentation)
Sync Tasks
1. Update Screen Count
When screens are added/removed:
Files to Update:
README.md: Update count in project descriptionREADME.ja.md: Update count (Japanese version)CLAUDE.md: Update count if mentioned
Example:
# Before
96+ visual effects screens
# After (when adding new screen)
97+ visual effects screens
2. Update Command Documentation
When Makefile commands change:
Files to Update:
README.md: Command reference sectionREADME.ja.md: Command reference sectionCLAUDE.md: Build & Development Commands section
Sync Steps:
- Read
Makefilefor all targets - Extract help text and descriptions
- Update command tables in README files
- Ensure examples match actual commands
Example Makefile Target:
.PHONY: new-screen
new-screen: ## Create new screen (interactive or with NAME=...)
@bash Scripts/new_screen.sh $(NAME) $(SHADER)
Corresponding Documentation:
| Command | Description |
|---------|-------------|
| `make new-screen` | Create new screen (interactive or with NAME=...) |
3. Update Architecture Documentation
When architecture changes:
Files to Update:
README.md: Architecture sectionCLAUDE.md: Architecture section
Key Areas:
- Module structure changes
- New patterns introduced
- SPM plugin updates
- Build system 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.
- 2mo ago First seen · 370 lines · 0 tokens per session scan A 4da8564ae32c
sync-docs is a command published in the GitHub repository Koshimizu-Takehito/my-toybox (118 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,945 tokens. 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-09-04.
sync-docs compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sync-docsKoshimizu-Takehito/my-toybox | Command | 118 | 6d ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |