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 Jamie-BitFlight/claude_skills --skill bash-testinggit clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/bash-testing)<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/bash-testing"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/bash-testing.svg" alt="Measured on agentmods" 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.00059 | $0.01867 |
| Opus 5 | $0.00030 | $0.00933 |
| Sonnet 5 | $0.00012 | $0.00373 |
| Haiku 4.5 | $0.00006 | $0.00187 |
Grade A, and why
bash-testing 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 4d 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 — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bash Testing
Testing frameworks and patterns for shell scripts, focusing on shunit2 and shellspec.
Framework Selection
| Framework | Strengths | Best For |
|---|---|---|
| shunit2 | xUnit style, simple, portable | Unit tests, function testing |
| shellspec | BDD style, modern, extensive | Behavior specs, full projects |
shunit2
Installation
# Download directly
curl -L https://github.com/kward/shunit2/raw/master/shunit2 -o shunit2
# Or via package manager
apt install shunit2
brew install shunit2
Basic Test Structure
#!/usr/bin/env bash
# Source the script being tested
source ./my_script.sh
# Test functions start with test
test_addition() {
result=$(add 2 3)
assertEquals "2 + 3 should equal 5" "5" "$result"
}
test_string_output() {
result=$(greet "World")
assertEquals "Hello, World" "$result"
}
test_file_creation() {
create_temp_file
assertTrue "Temp file should exist" "[ -f /tmp/testfile ]"
}
test_exit_code() {
validate_input "valid"
assertEquals "Should return 0 for valid input" 0 $?
}
# Setup and teardown
oneTimeSetUp() {
# Run once before all tests
export TEST_DIR=$(mktemp -d)
}
oneTimeTearDown() {
# Run once after all tests
rm -rf "$TEST_DIR"
}
setUp() {
# Run before each test
cd "$TEST_DIR"
}
tearDown() {
# Run after each test
rm -f "$TEST_DIR"/*
}
# Load shunit2
source shunit2
shunit2 Assertions
# Equality
assertEquals [message] expected actual
assertNotEquals [message] unexpected actual
# Null/Empty
assertNull [message] value
assertNotNull [message] value
# Boolean/Status
assertTrue [message] condition
assertFalse [message] condition
# Same reference (string comparison)
assertSame [message] expected actual
assertNotSame [message] unexpected actual
# Contains (in string)
assertContains [message] container content
# Exit status
assertEquals 0 $?
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.
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.
- 4d ago First seen · 383 lines · 59 tokens per session scan E 43acb4fa5240
bash-testing is a skill published in the GitHub repository Jamie-BitFlight/claude_skills (65 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,867 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-09-03.
Other skills, from other repositories
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
setup
Wire Ginkgo into a Go package — install the ginkgo CLI and Ginkgo+Gomega, ginkgo bootstrap to generate the suitetest.go (TestXxx/RegisterFailHandler(Fail)/RunSpecs), the package xxxtest convention, dot-import alternatives (aliased import, dsl/ subpackages, --nodot), ginkgo generate, and testing.T interop via…
assertions
Write correct synchronous Gomega assertions — Expect/Ω notation, the To/NotTo/ToNot/Should/ShouldNot equivalences, the multi-return error idiom, Succeed vs HaveOccurred, the .Error() chaining form, annotating assertions (format-string and func()string), tuning failure output via the format subpackage…
adk-setup
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test run. Runs only when explicitly requested, never on its own. Use when asked to set up, bootstrap, or repair a development…