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 LandonSchropp/agent-toolkit --skill bash-scriptgit clone --depth 1 https://github.com/LandonSchropp/agent-toolkitWrote 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/landonschropp/agent-toolkit/bash-script)<a href="https://agentmods.dev/skills/landonschropp/agent-toolkit/bash-script"><img src="https://agentmods.dev/badge/skills/landonschropp/agent-toolkit/bash-script/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/landonschropp/agent-toolkit/bash-script"><img src="https://agentmods.dev/badge/skills/landonschropp/agent-toolkit/bash-script.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.00035 | $0.00591 |
| Opus 5.5 | $0.00014 | $0.00236 |
| Sonnet 5.5 | $0.00007 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
bash-script 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Template
Two templates cover the two kinds of scripts. Copy the right one exactly and fill in the specific logic.
- Simple: Scripts intended to be run directly by a user. These typically take either no arguments or a single positional argument. Start from
assets/template-simple.sh. It shows the one-argument form; if the script takes no arguments, delete the argument check and keep the top comment. - Complex: Scripts capable of taking multiple arguments via flags. Skill scripts should always be considered complex scripts. Start from
assets/template-complex.sh. These always support--help.
Conventions
- File:
<name>.shwith kebab-case (e.g.,extract-pr-number.sh) - Make the file executable (
chmod +x) - Flag-based arguments using
--flag-name(kebab-case). Only use positional args for very simple cases. - Arguments are always required. Never make script arguments optional unless the user explicitly asks for it.
- Full variable names (
directory, notdir) - Call other commands with their long flags (
--session=main, not-s main), so the call reads without knowing the command - Exit
0for success,1for errors - stdout for primary output, stderr for errors/warnings/progress messages
- Run
shellcheckon the script when you finish editing it, not after every change - Let a call fail and exit via
set -euo pipefailinstead of wrapping it inif ! cmd; then. Only add an explicit check when the failure is actually likely or needs a clearer message than the default crash (most don't).
Required patterns
Always:
set -euo pipefailat the top of every script- All error messages must start with
Error:and go to stderr (>&2) - Always quote variable expansions (
"$variable")
Simple scripts:
- A top comment describing what the script does
- No
--helpflag - If it takes an argument, print a usage message to stderr and exit
1when the argument is missing
What ships with it
3 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 Changed · +1 lines b63f9981545f
- 1mo ago Changed · +1 lines · +15 tokens per session 1a6dc95511ca
- 1mo ago First seen · 49 lines · 20 tokens per session scan A fe9cc6ff73db
bash-script is a skill published in the GitHub repository LandonSchropp/agent-toolkit (3 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 591 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
authoring-go-sdk-tasks
Writes Airflow task logic in Go using the Airflow Go SDK. Use when the user wants to implement Airflow tasks in Go, asks about BundleProvider/RegisterDags, the bundlev1 Registry/Dag interfaces, registering Go tasks (AddTask/AddTaskWithName), dependency injection by parameter type (context.Context, sdk.TIRunContext…
authoring-java-sdk-tasks
Writes Airflow task logic in Java, Kotlin, or any JVM language using the Airflow Java SDK. Use when the user wants to implement Airflow tasks in Java/JVM, asks about @Builder.Dag/@Builder.Task/@Builder.XCom, the Task/BundleBuilder interfaces, reading connections/variables/XComs from Java, the JSON-to-Java type…
configuring-airflow-language-sdks
Configures Airflow to run language SDK tasks (Java, Go, and future native SDKs) — register a coordinator, map a queue to it, ensure the runtime/artifact on workers, and tune coordinator options. Use when the user wants Airflow to route a queue to a native-language coordinator, asks about the [sdk]…
authoring-dags
Workflow and best practices for writing Apache Airflow DAGs. Use when creating a new DAG, write pipeline code, handling questions about DAG patterns and conventions or extending an existing DAG with a follow-up/downstream task. ANY request shaped like 'add a DAG named X', 'write a pipeline', 'add a task that runs…
deploying-go-sdk-bundles
Builds, packs, and deploys compiled Airflow Go SDK bundles so the ExecutableCoordinator can run them. Use when the user wants to compile a Go task bundle, asks about go build, go tool airflow-go-pack, the AFBNDL01 self-contained executable bundle, packing or inspecting a bundle, placing it under executablesroot…
aws-sdk-java-v2-bedrock
Provides Amazon Bedrock patterns using AWS SDK for Java 2.x. Invokes foundation models (Claude, Llama, Titan), generates text and images, creates embeddings for RAG, streams real-time responses, and configures Spring Boot integration. Use when asking about Bedrock integration, Java SDK for AI models, AWS generative…