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 kouroshez/coding-os --skill shell-scriptinggit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/shell-scripting)<a href="https://agentmods.dev/skills/kouroshez/coding-os/shell-scripting"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/shell-scripting.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.00155 | $0.01876 |
| Opus 5 | $0.00077 | $0.00938 |
| Sonnet 5 | $0.00031 | $0.00375 |
| Haiku 4.5 | $0.00015 | $0.00188 |
Grade C, and why
shell-scripting scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ./* Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Wrong — pipefail off: the pipeline "succeeds" even though curl failed How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shell & CLI Scripting
A script is a contract: given inputs, do exactly one job, report a precise result, fail loud on anything unexpected. A script that hardcodes a path, swallows errors, or prints a paragraph the caller must parse is a liability — it breaks silently in the next environment and taxes every agent that runs it. This skill makes "robust, data-driven, observable" the default shape.
Scaffold a compliant script instead of hand-writing the boilerplate:
python3 scripts/new_script.py --lang bash --name deploy --root .Lint an existing one against the discipline:bash scripts/lint_script.sh path/to/script.sh
The seven non-negotiables
Every script — Bash or Python — satisfies all seven. The checklist in assets/script-checklist.md is the ship gate.
- Runtime arguments, never hardcoded. Inputs come from flags with sane defaults. No literal machine paths, no baked-in hostnames, no magic constants buried in the body.
- Fail-closed. Any unmet precondition or sub-command failure stops the script with a non-zero exit and a message — never continue on error.
- Idempotent. Re-running is safe: detect already-done state, refuse to clobber (or require
--force). - Observable. Progress to stderr for anything slow; a final, parseable result (one line or
--json) on stdout. - Precise output. stdout is the result a caller consumes; stderr is narration. Never mix them.
- Algorithmically honest. No O(n²) where a set/index is O(n). Stream large inputs; bound memory. State complexity when non-obvious.
- Documented header.
PURPOSE / INPUT / OUTPUT / DEPENDENCIES / NOTESat the top — the contract in five lines.
Bash — the robust preamble (copy, don't retype)
#!/usr/bin/env bash
# deploy.sh — PURPOSE: ... / INPUT: ... / OUTPUT: ... / DEPS: ... / NOTES: ...
set -euo pipefail # -e exit on error · -u unset var is error · -o pipefail catch piped failures
IFS=$'\n\t' # safe word-splitting (no space-splitting surprises)
cleanup() { rm -f "${_tmp:-}"; }
trap cleanup EXIT # run on ANY exit path — success, error, or signal
What ships with it
6 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.
- 4d ago First seen · 129 lines · 155 tokens per session scan C a16b6fa84938
shell-scripting is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 155 tokens to every session and 1,876 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it C 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-09-03.
Other skills, from other repositories
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
potpie-change-timeline
Use when an agent needs recent or historical change context: what changed recently, regressions, merged PRs, tickets, docs, incidents, deployments, releases, and source-history ingestion.
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.
potpie-project-preferences
Use before writing, modifying, reviewing, refactoring, or testing code so repo/project preferences surface: error handling, file structure, frameworks, logging, dependency choices, testing, security, API style, and naming. Also use after code work when a reusable project preference should be recorded.
memstack-deployment-ci-cd-pipeline
Use this skill when the user says 'CI/CD', 'GitHub Actions', 'pipeline', 'continuous integration', 'continuous deployment', 'ci-cd-pipeline', 'automate deploys', or needs to set up automated build, test, and deployment pipelines. Do NOT use for one-time manual deployments.