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/checkgit 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.00010 | $0.00438 |
| Opus 5 | $0.00005 | $0.00219 |
| Sonnet 5 | $0.00002 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
check 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 Status Check
Overview
Check dotfiles status including local changes, remote sync state, and shell sync checker status.
Capabilities:
- Detects local changes in managed dotfiles
- Checks remote repository sync state (ahead/behind)
- Verifies shell sync checker status
- Provides actionable next steps
Use when: "check dotfiles", "dotfiles status", "chezmoi status", "verify sync", "dotfiles確認", "同期状態チェック", "ステータス確認"
Don't use for: Project code status, general git status checks
Execution
以下のBashコマンドを即座に実行してください:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/chezmoi-check.sh
After execution, report the results to the user.
Reference: Script Behavior
The check script performs three steps:
Step 1: Local Changes Detection
- Runs
chezmoi statusto detect modified files - Reports files that differ between source state and target state
Step 2: Git Sync Status
- Fetches latest from origin/main
- Shows branch status (ahead/behind)
- Provides actionable next steps:
- If local changes + behind: sync first, then commit
- If local changes only: commit and push
- If behind only: sync to pull latest
- If ahead only: push commits
- If up-to-date: no action needed
Step 3: Shell Sync Checker Migration
- Checks for old embedded sync checker code in .zshrc
- Warns if outdated version detected (has macOS timeout bug)
- Suggests running
/chezmoi:shell-sync-setupto migrate
Error Handling
- Exits with error if chezmoi is not installed
- Provides installation instructions (
brew install chezmoi) - Detects if chezmoi source directory is not a git repository
- Suggests running
/chezmoi:setupfor initial configuration
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 · 59 lines · 10 tokens per session scan A 49f47f5f2cea
check is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 5d ago), licensed MIT. It adds 10 tokens to every session and 438 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-31.
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.