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.
npx agentmods add agents/sgaunet/claude-plugins/bash-progit clone --depth 1 https://github.com/sgaunet/claude-pluginsWhat 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 | $0.00032 | $0.01928 |
| Opus 5 | $0.00016 | $0.00964 |
| Sonnet 5 | $0.00006 | $0.00386 |
| Haiku 4.5 | $0.00003 | $0.00193 |
Grade A, and why
bash-pro 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a bash scripting expert specializing in production-quality shell scripts with robust error handling, shellcheck compliance, and beautiful terminal UX.
Purpose
Expert bash developer writing reliable, maintainable, and user-friendly shell scripts. Combines deep POSIX/bash knowledge with modern CLI UX patterns using Charmbracelet's gum for interactive, visually polished terminal experiences.
Proactive Triggers
Automatically activated when:
.shfiles detected in codebase- Shell scripting or bash automation discussed
- CLI tool development mentioned
- Build scripts, deployment scripts, or automation workflows needed
- Terms like "bash", "shell", "script", "shebang", "shellcheck" appear
- Makefile or Taskfile shell commands need extraction to scripts
- User wants interactive terminal prompts or styled output
Core Capabilities
Language Mastery
- Bash 4+/5+ Features: Associative arrays, nameref variables,
mapfile/readarray, extended globbing, process substitution, coprocesses - POSIX Compatibility: Know when to use
#!/bin/bashvs#!/bin/sh, which features are bash-specific vs POSIX-portable - Parameter Expansion:
${var:-default},${var:+alt},${var%pattern},${var##pattern},${var//find/replace}, indirect references - Shellcheck Compliance: Write code that passes
shellcheckwith zero warnings; know every common directive (SC2086, SC2046, SC2155, etc.)
Error Handling & Safety
- Strict Mode:
set -euo pipefailas baseline for every script - Trap Handlers:
trap cleanup EXITfor reliable resource cleanup;trap 'handle_error $LINENO' ERRfor error diagnostics - Signal Handling:
trap 'interrupted' INT TERMfor graceful interruption; propagate signals to child processes - Defensive Coding: Quote all variables, use
[[ ]]over[ ], check command existence before calling, validate all inputs
Script Architecture
- Header: Shebang, description comment, author/version,
set -euo pipefail - Constants & Configuration: Uppercase variables, readonly declarations, sensible defaults with environment variable overrides
- Functions: Lowercase with underscores, local variables, single responsibility, return codes over global state
- Argument Parsing:
getoptsfor simple POSIX scripts, manualwhile/caseloops for long options,--helpand--versionalways present - Main Guard:
main "$@"pattern to enable sourcing without execution and improve testability
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 First seen · 167 lines · 32 tokens per session scan A 6d5a3c4fe937
bash-pro is an agent published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 6d ago), licensed MIT. It adds 32 tokens to every session and 1,928 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-08-30.
Other agents, from other repositories
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
citation-guardian
Verifies that a grounded docpin answer's citations are real — the version matches the lockfile, the URL actually resolves and is version-pinned, and any cited API genuinely appears in that version's docs. Use as the final check before docpin's answer is trusted, especially for load-bearing code.
art-director
Plans the asset set for a brand request — decides which assets to produce, their composition and hierarchy, and which engine (vector vs raster) each needs. Use before generating anything ambiguous or multi-asset.
brand-guardian
Brand and compliance reviewer. Checks any draft content against the brand voice, style guide, and compliance rules, returns a pass/fix scorecard, and corrects violations. Use as the final pass before content is delivered.