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/setupgit 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.00018 | $0.01808 |
| Opus 5 | $0.00009 | $0.00904 |
| Sonnet 5 | $0.00004 | $0.00362 |
| Haiku 4.5 | $0.00002 | $0.00181 |
Grade D, and why
setup scanned grade D with 2 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 yesterday.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 ~/.config/chezmoi/key.txt Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
chezmoi add --encrypt ~/.ssh/id_rsa How it starts
The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chezmoi Setup Wizard
Overview
Interactive setup guide for chezmoi dotfiles management with age encryption and 1Password integration.
Capabilities:
- Guides through 5-phase setup
- Supports age encryption and 1Password integration
- Handles both new setup and clone existing scenarios
Use when: "set up chezmoi", "configure dotfiles", "initialize chezmoi", "first time setup", "new machine setup", "chezmoi初期設定", "dotfiles設定", "1Password連携", "初回セットアップ"
Don't use for: Updating existing dotfiles, syncing changes, checking status
5 Phases:
- Environment check (tools availability)
- Detect existing setup
- Setup mode selection (new vs clone)
- Guided setup (new machine or clone existing)
- Verification
Execution
Follow the 5 phases sequentially. Read the Reference sections for detailed instructions.
Phase 1: Environment Check
Check if required tools are installed (see Reference: Phase 1 below).
Phase 2: Detect Existing Setup
Check if chezmoi is already configured (see Reference: Phase 2 below).
Phase 3: Mode Selection
Based on existing setup, ask user which mode to proceed with (see Reference: Phase 3 below).
Phase 4: Setup Guide
Based on selection:
- New setup (first machine): See Reference: Phase 4A below
- Clone existing (second+ machine): See Reference: Phase 4B below
Phase 5: Verification
After setup, verify everything works (see Reference: Phase 5 below).
Reference: Phase 1 - Environment Check
Check if required tools are installed:
echo "🔍 Checking required tools..."
echo ""
# Check chezmoi
if command -v chezmoi &> /dev/null; then
echo "✅ chezmoi: $(chezmoi --version)"
else
echo "❌ chezmoi: Not installed"
echo " Install with: brew install chezmoi"
fi
# Check age
if command -v age &> /dev/null; then
echo "✅ age: $(age --version 2>&1 | head -1)"
else
echo "❌ age: Not installed"
echo " Install with: brew install age"
fi
# Check 1Password CLI
if command -v op &> /dev/null; then
echo "✅ op: $(op --version)"
else
echo "⚠️ op: Not installed (optional)"
echo " Install with: brew install --cask 1password-cli"
fi
# Check GitHub CLI
if command -v gh &> /dev/null; then
echo "✅ gh: $(gh --version | head -1)"
else
echo "⚠️ gh: Not installed (optional)"
echo " Install with: brew install gh"
fi
echo ""
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.
- yesterday First seen · 289 lines · 18 tokens per session scan D 688b3ead6ff5
setup is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 1,808 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, reaches for credential files). 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.