language-bash

language-bash is a skill for Claude Code from lugassawan/swe-workbench. It costs 60 tokens per session (1,809 once invoked), scanned A, original, MIT.

A skill that teaches Bash, the command-line shell used for writing scripts, including safer syntax, variables, arrays, cleanup, and portable commands.

In plain words
What is it for?
It is for writing, reviewing, and checking .sh and .bash files, including scripts that use strict mode or ShellCheck.
Why use it?
It helps prevent common shell-script mistakes such as broken error handling, unsafe word splitting, and failures caused by missing values.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the swe-workbench plugin — 61 skills, 25 commands, 23 agents, 4 hooks shipped together

Good fit It is for writing, reviewing, and checking .sh and .bash files, including scripts that use strict mode or ShellCheck.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lugassawan/swe-workbench/language-bash
Install

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.

Any agent
npx skills add lugassawan/swe-workbench --skill language-bash
Clone the repo
git clone --depth 1 https://github.com/lugassawan/swe-workbench

Made for: Claude Code.

Or install swe-workbench, the plugin that ships this one along with the rest of its 61 skills, 25 commands, 23 agents, 4 hooks.

Wrote 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.

agentmods badge for language-bash

README.md
[![agentmods](https://agentmods.dev/badge/skills/lugassawan/swe-workbench/language-bash/github.svg)](https://agentmods.dev/skills/lugassawan/swe-workbench/language-bash)
Your own site
<a href="https://agentmods.dev/skills/lugassawan/swe-workbench/language-bash"><img src="https://agentmods.dev/badge/skills/lugassawan/swe-workbench/language-bash/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.

agentmods 80×15 button for language-bash

Your own site · 80×15
<a href="https://agentmods.dev/skills/lugassawan/swe-workbench/language-bash"><img src="https://agentmods.dev/badge/skills/lugassawan/swe-workbench/language-bash.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,809 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00060 $0.01809
Opus 5.5 $0.00024 $0.00724
Sonnet 5.5 $0.00012 $0.00362
Haiku 4.5 $0.00006 $0.00181

Measured 1mo ago against content hash 932a1297a598, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

language-bash 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 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.

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.

skills/language-bash/SKILL.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bash

Strict mode

set -euo pipefail
IFS=$'\n\t'
  • -e is suppressed in conditional contexts (||, &&, if, !); explicit subshells (...) do inherit it — use || true to absorb expected failures.
  • -u treats unset variables as errors; unset arrays trigger it: declare before use (arr=()) or guard with ${arr[@]+"${arr[@]}"} for optional arrays.
  • IFS=$'\n\t' prevents accidental word-splitting on spaces in for loops and command substitution.

Quoting and tests

  • Always "$var" — bare $var triggers word splitting and glob expansion.
  • 'literal' for fixed strings with no expansion needed.
  • Prefer [[ ]] over [ ]: supports =~ regex, no word splitting, lexical string comparison.
  • $() over backticks: nestable, readable, no escaping required.
if [[ "$filename" =~ \.(sh|bash)$ ]]; then
  shellcheck "$filename"
fi

Parameter expansion

  • ${var:-default} — substitute default if unset or empty.
  • ${var:?error msg} — abort with message if unset; pairs well with set -u.
  • ${var%suffix} — strip shortest suffix match (e.g. strip extension).
  • ${var//pattern/repl} — replace all occurrences in-place.

Arrays and word splitting

files=(src/a.sh "src/b script.sh" src/c.sh)
for f in "${files[@]}"; do   # each element quoted separately
  process "$f"
done
  • "${arr[@]}" — each element as a separate quoted word; always use for iteration.
  • "${arr[*]}" — all elements joined by IFS[0]; use only for joining to a string.
  • Never for x in $(cmd) — use mapfile -t arr < <(cmd) or while IFS= read -r line.

Pipelines and subshells

  • pipefail makes a pipeline fail when any stage fails, not just the last.
  • Command substitution $(...) runs in a subshell; variable assignments inside don't leak out.
  • cmd || true absorbs an expected non-zero exit under -e; cmd 2>/dev/null suppresses stderr noise separately.
  • Background jobs: proc &; always wait "$pid" before consuming results.
  • Redirect ordering matters: cmd >/dev/null 2>&1 silences all; cmd 2>&1 >/dev/null silences stdout only (stderr still shows — order determines what 2>&1 copies).

Read the full file on GitHub · 138 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 1mo ago First seen · 138 lines · 60 tokens per session scan A 932a1297a598

Subscribe to this mod's changes

language-bash is a skill published in the GitHub repository lugassawan/swe-workbench (3 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 1,809 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

functions-development

Build serverless Go or Python functions for Falcon Foundry apps. TRIGGER when user asks to "create a function", "write a serverless function", "build backend logic", runs foundry functions create, or needs help with FDK handler patterns, function testing, or collection integration from functions. Also TRIGGER when…

CrowdStrike/foundry-skills · 195 tokens

golang-troubleshooting

Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve debugger, race detection, GODEBUG tracing, and production…

emilioforrer/go-stack · 108 tokens

golang-benchmark

Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with…

emilioforrer/go-stack · 94 tokens

golang-safety

Defensive Golang coding to prevent panics, silent data corruption, and subtle runtime bugs. Use whenever writing or reviewing Go code that involves nil-prone types (pointers, interfaces, maps, slices, channels), numeric conversions, resource lifecycle (defer in loops), or defensive copying. Also triggers on questions…

emilioforrer/go-stack · 89 tokens

golang-samber-oops

Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports…

emilioforrer/go-stack · 74 tokens

golang-lint

Provides linting best practices and golangci-lint configuration for Go projects. Covers running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and managing linter settings. Use this skill whenever the user runs linters, configures golangci-lint, asks about…

emilioforrer/go-stack · 122 tokens