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 skills add JayRHa/AgentSkills --skill bash-script-hardeninggit clone --depth 1 https://github.com/JayRHa/AgentSkillsWrote 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/jayrha/agentskills/bash-script-hardening)<a href="https://agentmods.dev/skills/jayrha/agentskills/bash-script-hardening"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/bash-script-hardening/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/jayrha/agentskills/bash-script-hardening"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/bash-script-hardening.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.00100 | $0.02235 |
| Opus 5.5 | $0.00040 | $0.00894 |
| Sonnet 5.5 | $0.00020 | $0.00447 |
| Haiku 4.5 | $0.00010 | $0.00224 |
Grade B, and why
bash-script-hardening scanned grade B with 2 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 1mo 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
[[ -n "${tmpdir:-}" && -d "$tmpdir" ]] && rm -rf -- "$tmpdir" Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
require_cmd curl How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bash Script Hardening
Overview
Most Bash bugs are silent: an unset variable expands to nothing, a failed command is ignored, an unquoted path word-splits, and the script marches on corrupting state. This skill makes Bash scripts fail loudly, fail early, and clean up after themselves.
Keywords: bash, shell, strict mode, set -euo pipefail, IFS, quoting, word splitting, globbing, ShellCheck, trap, ERR, EXIT, cleanup, mktemp, signal handling, defensive scripting, POSIX, exit codes, here-doc, arrays.
Use this skill to author a new script from a hardened template, retrofit an existing script, or review a script for safety defects.
Workflow
- Set the shebang and strict mode. Use
#!/usr/bin/env bashand the canonical strict-mode preamble (see below). Never rely on/bin/shif Bash features are used. - Lock down word splitting. Set
IFS=$'\n\t'so unquoted expansions don't split on spaces. - Quote everything. Every variable expansion and command substitution gets double quotes unless you have a deliberate, commented reason not to.
- Use arrays for lists and command arguments. Never build commands by concatenating strings.
- Add a cleanup trap. Register an
EXITtrap that removes temp files and restores state, plus anERRtrap for diagnostics. - Handle errors explicitly where strict mode is insufficient (conditionals, command substitution in older Bash, pipelines you intend to tolerate).
- Create temp files safely with
mktemp, and reference them through the cleanup trap. - Validate inputs and dependencies up front: required args, required commands (
command -v), required env vars. - Run ShellCheck and resolve every finding; suppress only with a justified
# shellcheck disable=SCxxxxcomment. - Test failure paths, not just the happy path.
Reference files:
references/strict-mode.md— deep dive onset -euo pipefail, IFS, and the gotchas/escape hatches.references/shellcheck-codes.md— the most common ShellCheck codes, what they mean, and the correct fix.templates/hardened-script.sh— drop-in starting template with strict mode, traps, arg parsing, logging.scripts/harden_check.sh— static auditor that flags missing strict mode, unquoted vars, and other red flags.examples/before-after.md— a real fragile script transformed into a hardened one, line by line.
What ships with it
5 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.
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.
- 1mo ago First seen · 160 lines · 100 tokens per session scan B 1e75ea939b26
bash-script-hardening is a skill published in the GitHub repository JayRHa/AgentSkills (12 stars, last pushed 2mo ago), licensed MIT. It adds 100 tokens to every session and 2,235 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cost-optimizer
Trigger when the user asks to audit Claude Code costs, reduce token spend, says "my Claude bill is too high", "optimize my CLAUDE.md", "why is this project burning tokens", or "/cost-optimizer". Scans a project for the common Claude Code cost leaks and returns a prioritized fix list.
excalidraw-architecture
Trigger when the user asks for an architecture diagram, says "draw the system", "update the architecture diagram", "give me an excalidraw of this codebase", or "/excalidraw-architecture". Generates or updates an Excalidraw JSON file at docs/architecture.excalidraw by reading the codebase's key entry points.
model-cost-compare
Trigger when the user asks which model to use, wants to compare model costs, says "what's cheapest for this task", "should I use Opus or Sonnet", "can a smaller model handle this", or "/model-cost-compare". Estimates token cost across Opus 4.6, Sonnet 4.6, GLM-5.1, Minimax M2.7, and local Gemma 4, then recommends the…
openclaw-debugger
Trigger when an OpenClaw agent is broken, silent, crashing, stuck, not responding, returning empty output, or the user says "my agent is down", "agent not working", "/openclaw-debugger". Walks through the standard OpenClaw 2026.4 diagnosis checklist and prints a report.
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.
growth-ideas
Describe your product or project and get three actionable growth ideas tailored to your stage.