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/JosiahSiegel/claude-plugin-marketplaceWrote 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/josiahsiegel/claude-plugin-marketplace/bash-analyze)<a href="https://agentmods.dev/commands/josiahsiegel/claude-plugin-marketplace/bash-analyze"><img src="https://agentmods.dev/badge/commands/josiahsiegel/claude-plugin-marketplace/bash-analyze/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/josiahsiegel/claude-plugin-marketplace/bash-analyze"><img src="https://agentmods.dev/badge/commands/josiahsiegel/claude-plugin-marketplace/bash-analyze.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.00020 | $0.00933 |
| Opus 5 | $0.00010 | $0.00466 |
| Sonnet 5 | $0.00004 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
bash-analyze 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 10d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL GUIDELINES
Windows File Path Requirements
MANDATORY: Always Use Backslashes on Windows for File Paths
When using Edit or Write tools on Windows, you MUST use backslashes (\) in file paths, NOT forward slashes (/).
Bash Script Analyzer
Purpose
Perform comprehensive analysis of bash scripts covering security vulnerabilities, performance issues, portability concerns, and adherence to modern best practices.
Analysis Categories
1. Security Analysis
- Command injection vulnerabilities
- Path traversal risks
- Unsafe temporary file handling
- Unquoted variable expansions
- Privilege escalation risks
- Sensitive data exposure
- Race condition vulnerabilities
2. Performance Analysis
- Unnecessary subshell spawning
- Inefficient loops (UUOC, UUOG)
- External command overuse vs bash builtins
- Pipeline optimization opportunities
- Array usage efficiency
- Process substitution opportunities
3. Portability Analysis
- Bash version compatibility (4.x, 5.x features)
- POSIX compliance level
- Platform-specific issues (Linux/macOS/BSD)
- GNU vs BSD tool differences
- Shebang portability
4. Best Practices Compliance
- ShellCheck warnings (all severity levels)
- Google Shell Style Guide adherence
- Error handling patterns
- Cleanup and trap usage
- Function structure and modularity
- Documentation and comments
Analysis Output Format
For each script analyzed, provide:
## Script: <filename>
### Security Issues
- [CRITICAL] <issue description>
- [HIGH] <issue description>
- [MEDIUM] <issue description>
### Performance Issues
- [IMPACT: HIGH] <issue description>
- [IMPACT: MEDIUM] <issue description>
### Portability Issues
- [Bash 5.x required] <feature used>
- [GNU-specific] <command/flag used>
### Best Practice Violations
- [ShellCheck SC####] <description>
- [Style] <description>
### Recommendations
1. <actionable recommendation>
2. <actionable recommendation>
### Score: X/100
- Security: X/25
- Performance: X/25
- Portability: X/25
- Best Practices: X/25
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.
- 10d ago First seen · 164 lines · 20 tokens per session scan A 3062f6e29679
bash-analyze is a command published in the GitHub repository JosiahSiegel/claude-plugin-marketplace (54 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 933 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-30.
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…
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…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.