Borrowing it
Nothing to install: this file belongs to vlad-ryzhkov/ai-context-engineering-for-qa. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vlad-ryzhkov/ai-context-engineering-for-qa/main/.claude/skills/bash-reviewer/SKILL.mdgit clone --depth 1 https://github.com/vlad-ryzhkov/ai-context-engineering-for-qaWrote 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/skills/vlad-ryzhkov/ai-context-engineering-for-qa/bash-reviewer)<a href="https://agentmods.dev/skills/vlad-ryzhkov/ai-context-engineering-for-qa/bash-reviewer"><img src="https://agentmods.dev/badge/skills/vlad-ryzhkov/ai-context-engineering-for-qa/bash-reviewer/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/skills/vlad-ryzhkov/ai-context-engineering-for-qa/bash-reviewer"><img src="https://agentmods.dev/badge/skills/vlad-ryzhkov/ai-context-engineering-for-qa/bash-reviewer.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.00068 | $0.02980 |
| Opus 5 | $0.00034 | $0.01490 |
| Sonnet 5 | $0.00014 | $0.00596 |
| Haiku 4.5 | $0.00007 | $0.00298 |
Grade A, and why
bash-reviewer 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 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.
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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bash-reviewer — Shell Script Anti-Pattern Reviewer
SILENT MODE: Execute all analytical phases silently. Do not output intermediate reasoning, progress updates, or conversational filler. Output ONLY the structured issue blocks and summary. Exception: if no issues found, output a single line:
✅ No anti-patterns detected
When to Use
- User asks to review, audit, or check shell scripts for quality
- Before merging PRs that add or modify
.shfiles - When diagnosing flaky or platform-dependent script failures
- When hardening scripts that run in CI/CD pipelines
When NOT to Use
- Python, Ruby, Go, or other non-shell scripts
- GitHub Actions YAML — use
/workflow-expertinstead - Issues already caught by shellcheck (quoting, SC2068, SC2086)
- One-liner shell commands in Makefiles or Dockerfiles
Scope
DO review:
.shand.bashfiles- Security: eval injection, unvalidated command expansion
- Portability: sed -i, grep -P, readarray/mapfile, find -o precedence
- Robustness: division by zero, wc in arithmetic, missing prerequisite checks, set -euo pitfalls
- DRY: repeated check/counter blocks, duplicated scan loops, shared constants across files
DON'T review:
- Style preferences (indentation, naming conventions)
- ShellCheck-detectable issues (quoting, word splitting)
- Logic correctness of the script's business domain
Detection Workflow
Step 1: Discover Scripts
Use Glob to find all .sh and .bash files in the target path.
If user specified a single file, skip discovery.
Step 2: Scan for Anti-Patterns
For each script, use Grep to scan for pattern signatures:
| Signal | Grep Pattern | Category |
|---|---|---|
eval |
eval\s |
Security |
$command used as execution |
^\s*\$\w+ |
Security |
sed -i |
sed\s+-i |
Portability |
grep -P |
grep\s+.*-P |
Portability |
readarray / mapfile |
readarray|mapfile |
Portability |
find with -o |
find\s.*-o\s |
Portability |
| Division in arithmetic | \$((.*/.*) |
Robustness |
wc -l in arithmetic context |
wc\s+-l |
Robustness |
set -.*u with arrays |
set\s+-.*u |
Robustness |
pipefail with grep |
pipefail |
Robustness |
| Tool usage without guard | jq|yq|shellcheck|docker|kubectl |
Robustness |
| Inverted return codes | return 0.*fail|return 0.*error |
Robustness |
set -e in WARN-only script |
set -.*e.*pipefail |
Robustness |
| Variable as regex in grep | grep ".*\$\w|grep \$\{ |
Security |
| Relative symlink in hooks | ln -s .*\.\./ |
Robustness |
| sed for YAML/JSON parsing | sed.*---.*---|sed.*^[a-z]*: |
Robustness |
| CLI arg into path w/o guard | --\w+.*"\$2".*|\$\{[A-Z_]+\}/\$\{ |
Security |
| Substring placeholder-exclude | your_|example_|placeholder |
Security |
| Case-restricted security cls | \[A-Z_\].*(TOKEN|KEY|SECRET) |
Security |
| Text-only extension filter | find.*-name.*\.md.*-o.*-name.*\.sh |
Security |
| Suppression w/o allowlist | is_nolint|is_suppressed|# noqa |
Security |
| Repeated check+counter block | check_result=\$\? |
DRY |
| Repeated scan/grep loop | while.*read.*grep.*done |
DRY |
| Repeated format+counter | \(\(.*\+\+\)\).*|| true |
DRY |
| Duplicated constants/utils | RED=.*033 in multiple files |
DRY |
| Missing shellcheck source | source.*\.sh |
Robustness |
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/arithmetic-guards.md 1.5 KB
- references/cli-arg-path-traversal.md 3.0 KB
- references/dry-patterns.md 4.4 KB
- references/eval-injection.md 1.5 KB
- references/find-operator-precedence.md 1.3 KB
- references/portable-sed-and-tools.md 1.7 KB
- references/prerequisite-checks.md 1.7 KB
- references/return-code-convention.md 2.1 KB
- references/security-scanner-fn.md 5.6 KB
- references/set-euo-pitfalls.md 2.2 KB
- references/shared-libs-and-structure.md 3.8 KB
- references/subprocess-caching.md 2.7 KB
- references/variable-as-regex.md 6.2 KB
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 Changed · +5 lines 084942b88dbd
- 10d ago First seen · 223 lines · 68 tokens per session scan A 99e3d3c3838f
bash-reviewer is a skill published in the GitHub repository vlad-ryzhkov/ai-context-engineering-for-qa (6 stars, last pushed today), licensed Unlicense. It adds 68 tokens to every session and 2,980 once invoked, about $0.0003 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 skills, from other repositories
effective-kotlin
Apply Effective Kotlin best practices (Marcin Moskała, 2nd Ed). Covers Safety (Items 1-10: mutability, scope, nulls, types, expectations, errors, resources, tests), Readability (Items 11-18: operators, receivers, properties, naming), Reusability (Items 19-25: DRY, generics, delegation, variance), Abstraction (Items…
cat:stakeholder-review
Multi-perspective quality review gate with architect, security, quality, tester, and performance stakeholders.
render-diff
MANDATORY: Use BEFORE showing ANY diff to user - transforms git diff into 4-column table with box characters (╭╮╰╯│). Required for approval gates, code reviews, change summaries.
debriefing-code-changes
Debriefs a developer after an AI-assisted coding session by inspecting git diffs or commits, explaining the actual architecture decisions, design patterns, tradeoffs, caveats, and learning concepts with file/function references, then generating a practical quiz and follow-up study notes. Use when the user says they…
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
review
Validate plans, execution, or PRs against wish criteria — returns SHIP / FIX-FIRST / BLOCKED with severity-tagged gaps.