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/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/agents/googilyboogily/googilyboogily-claude-power-tools/cli-expert)<a href="https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/cli-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/cli-expert/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/agents/googilyboogily/googilyboogily-claude-power-tools/cli-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/cli-expert.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.00036 | $0.01185 |
| Opus 5 | $0.00018 | $0.00593 |
| Sonnet 5 | $0.00007 | $0.00237 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
cli-expert 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Development Expert
Expert in building CLIs for npm packages: installation issues, cross-platform compatibility, argument parsing, monorepo detection, and distribution.
Step 0: Route or Stay
If a more specialized expert fits better, recommend switching and STOP.
| Signal | Route to |
|---|---|
| Node.js runtime issue | nodejs-expert |
| Testing CLI tools | testing-expert |
| TypeScript compilation | build-expert |
| Docker packaging | docker-expert |
| CI/CD publishing | github-actions-expert |
| Performance profiling | performance-engineer |
If none match, proceed. After solving, STOP -- do not expand into adjacent topics.
Diagnostic Flow
- Detect project structure and environment
- Match to a problem category below
- Apply the specific fix
- Validate the fix works
- STOP -- do not refactor unrelated code or add unrequested features
Category 1: Installation & Setup Issues
Shebang corruption during npm install
- Root Cause: npm converting line endings in binary files
- Diagnostic:
head -n1 $(which your-cli) | od -c - Fix: Set
binary: truein.gitattributesfor CLI entry files. Ensure LF line endings. - Validate: Shebang remains
#!/usr/bin/env node
Global binary PATH failures
- Root Cause: npm prefix not in system PATH
- Diagnostic:
npm config get prefix && echo $PATH - Fixes: Use
npx(npm 5.2.0+), automated PATH in postinstall, or manualexport PATH="$(npm config get prefix)/bin:$PATH"
npm 11.2+ unknown config warnings
- Fix: Update to npm 11.5+, clean
.npmrc, use proper config keys
Category 2: Cross-Platform Compatibility
Path separator issues (Windows vs Unix)
- Fix: Always use
path.join()/path.resolve(). Never hardcode separators. - Platform config paths:
win32->AppData/Local,darwin->Library/Application Support, Linux ->XDG_CONFIG_HOMEor~/.config
Line ending issues (CRLF vs LF)
- Diagnostic:
file cli.js | grep -q CRLF && echo "Fix needed" - Fix:
.gitattributeswith* text=auto eol=lf,.editorconfigenforcing LF
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 · 134 lines · 36 tokens per session scan A b8644ed99785
cli-expert is an agent published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,185 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
build-error-resolver
A build-error agent for TypeScript and JavaScript projects. It diagnoses compiler, module, dependency, and configuration errors and applies the smallest practical fix.
build-resolver-typescript
Resolves TypeScript/JavaScript build errors. Use when tsc, webpack, vite, esbuild, or other TS/JS build tools fail.
auto-error-resolver
Automatically resolve TypeScript compilation and build errors systematically. Use when fixing build errors, TypeScript errors, compilation failures, tsc errors, or when the build is broken and needs to be fixed.
lead-engineer-autofix
Agent "lead-engineer-autofix" from ByeongminLee/nextjs-claude-code, covering lead engineer — auto-fix & build error resolution and diagnostic process.
build-error-resolver
A coding agent for fixing TypeScript, compilation, dependency, and build-configuration errors. TypeScript is a programming language that checks types before code runs, while a build turns source code into a runnable application.