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.
git clone --depth 1 https://github.com/ArkTechNWA/zsh-toolWrote 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/arktechnwa/zsh-tool/zsh-tool-config)<a href="https://agentmods.dev/commands/arktechnwa/zsh-tool/zsh-tool-config"><img src="https://agentmods.dev/badge/commands/arktechnwa/zsh-tool/zsh-tool-config.svg" alt="Measured on agentmods" 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.00011 | $0.00377 |
| Opus 5 | $0.00005 | $0.00188 |
| Sonnet 5 | $0.00002 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
zsh-tool-config 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 8d 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
zsh-tool Config
Configure your zsh-tool defaults based on your Claude subscription tier.
Steps
-
Ask user for their subscription tier using AskUserQuestion:
- Header: "Timeout"
- Question: "Select your Claude subscription tier for optimal zsh-tool performance:"
- Options:
- Pro/Max (2s) - Faster feedback loop, more responsive. Recommended for Pro and Max subscribers.
- Free (30s) - Budget-friendly, fewer API round-trips. Works great, just slower feedback.
- Custom - Enter your own yield_after value in seconds.
-
If Custom selected, ask for the custom value (1-60 seconds).
-
Create config directory if needed:
~/.config/zsh-tool/ -
Write config file to
~/.config/zsh-tool/config.yaml:# zsh-tool configuration # Generated by /zsh-tool-config # # yield_after: Seconds before returning control (command continues in background) # Recommended by plan: # Pro/Max: 2 (faster iterations) # Free: 30 (budget-friendly) # yield_after: <selected_value> -
Confirm to user: "Configuration saved! zsh-tool will use {X}s yield timeout. Restart Claude Code for changes to take effect."
Notes
- Config file location:
~/.config/zsh-tool/config.yaml - This is a global user setting, not per-project
- Changes require Claude Code restart to take effect
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.
- 8d ago First seen · 44 lines · 11 tokens per session scan A b664edbadc77
zsh-tool-config is a command published in the GitHub repository ArkTechNWA/zsh-tool (4 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 377 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
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
amp-register
Register your agent with an external AMP provider for cross-provider messaging.
speckit.spec-stats.open
On-demand view of everything not complete: what stage each is stuck at, what the immediate next artifact/command is, oldest-untouched first, stale warnings past staleafterdays.
search
Full-text search the carrel desk index (FTS5, bm25-ranked) for local files matching a query, with type and tag filters.