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/signalcompose/claude-tools/syncgit clone --depth 1 https://github.com/signalcompose/claude-toolsWhat 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.00009 | $0.00518 |
| Opus 5 | $0.00005 | $0.00259 |
| Sonnet 5 | $0.00002 | $0.00104 |
| Haiku 4.5 | $0.00001 | $0.00052 |
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 2d 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.
What it actually says
Chezmoi Sync
Overview
Sync dotfiles from remote repository and apply changes.
Capabilities:
- Fetches latest dotfiles from remote repository
- Applies changes to local system
- Handles merge conflicts and errors
Use when: "sync dotfiles", "pull dotfiles", "update dotfiles", "fetch dotfiles", "apply changes", "dotfiles同期", "リモートから取得", "変更を適用"
Don't use for: Committing local changes, initial setup, checking status
Execution
Step 1: Fetch and Apply
chezmoi update で git pull + apply を自動実行。以下のBashコマンドを即座に実行してください:
chezmoi update -v
Step 2: Report Results
適用されたファイルをユーザーに報告。
Reference: Diff Interpretation
Important: chezmoi diff shows "what would happen if you run chezmoi apply".
-lines = Current local file content (destination)+lines = Chezmoi source content (what would be applied)
Example
- "plugin-x": true,
- "plugin-y": true
+ "plugin-x": true
Interpretation: Local has plugin-y, but chezmoi source does not.
| Situation | Action |
|---|---|
| Local has changes you want to keep | Run /chezmoi:commit to push to source |
| Source has updates you want | Run chezmoi apply to apply to local |
Reference: Error Handling
Network Error
Cannot reach github.com
Please check your internet connection and try again.
Git Conflict
Git conflict detected!
You have local changes that conflict with remote changes. Resolve conflicts manually:
cd ~/.local/share/chezmoigit status- Resolve conflicts
git add .git commitchezmoi apply
Notes
chezmoi updateautomatically runs git pull and chezmoi apply- If there are uncommitted local changes, an error may occur
- In that case, run
/chezmoi:commitfirst
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.
- 2d ago First seen · 87 lines · 9 tokens per session scan A 8be75869526b
sync is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 5d ago), licensed MIT. It adds 9 tokens to every session and 518 once invoked, about $0.0000 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-31.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.