Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add signalcompose/claude-tools/plugin install chezmoiWrote 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/signalcompose/claude-tools/diagnose-timeout)<a href="https://agentmods.dev/commands/signalcompose/claude-tools/diagnose-timeout"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/diagnose-timeout/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/signalcompose/claude-tools/diagnose-timeout"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/diagnose-timeout.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.00013 | $0.00473 |
| Opus 5.5 | $0.00005 | $0.00189 |
| Sonnet 5.5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
diagnose-timeout 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 1mo 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
Diagnose chezmoi status Timeout
This command helps diagnose why chezmoi status is slow by measuring timing for different operations.
Usage
以下のBashコマンドを即座に実行してください:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/diagnose-timeout.sh
What it measures
The diagnostic script measures:
- Template Expansion: Time to expand templates (includes 1Password API, Age decryption)
- Git Status: Time for git operations in the chezmoi source directory
- Overall chezmoi status: Total time for the full status check
- Network Connectivity: Checks if network latency affects 1Password API
Output Example
━━━ [chezmoi] Timeout Diagnosis ━━━
1. Template expansion: 3.2s
→ High (includes 1Password API, Age decryption)
2. Git status: 0.1s
→ Normal
3. chezmoi status (total): 3.8s
→ Timeout threshold: 30s
Bottleneck: Template expansion (1Password/Age)
Recommendations:
- Increase timeout: export CHEZMOI_STATUS_TIMEOUT=60
- Optimize 1Password API calls
- Consider caching template results
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Common Causes
| Cause | Impact | Solution |
|---|---|---|
| 1Password API | High | Cache results, reduce API calls |
| Age encryption | Medium-High | Optimize encrypted files |
| Git operations | Low-Medium | Check repository size |
| Network latency | Variable | Use offline mode or caching |
Next Steps
After diagnosing:
- If timeout is acceptable: Increase
CHEZMOI_STATUS_TIMEOUT - If bottleneck identified: See
docs/troubleshooting-timeout.mdfor solutions - If performance unexplained: Consider optimizing chezmoi configuration
Related
CHEZMOI_STATUS_TIMEOUTenvironment variable/chezmoi:check- Manual status checkdocs/troubleshooting-timeout.md- Detailed troubleshooting guide
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.
- 1mo ago First seen · 71 lines · 13 tokens per session scan A b3922790c884
diagnose-timeout is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 473 once invoked, about $0.0001 per session on Opus 5.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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.