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 TypedDevs/bashunit --skill pre-releasegit clone --depth 1 https://github.com/TypedDevs/bashunitWrote 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/typeddevs/bashunit/pre-release)<a href="https://agentmods.dev/skills/typeddevs/bashunit/pre-release"><img src="https://agentmods.dev/badge/skills/typeddevs/bashunit/pre-release/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/typeddevs/bashunit/pre-release"><img src="https://agentmods.dev/badge/skills/typeddevs/bashunit/pre-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 78 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00009 | $0.00494 |
| Opus 5.5 | $0.00004 | $0.00198 |
| Sonnet 5.5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
pre-release 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 5d 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.
What it actually says
Pre-release validation
Assess readiness without publishing. Repository paths are relative to the repository root. Use {{$SKILL:release}} for publishing; release.sh owns version changes, tags and uploads.
- Start on clean, current
main. ReadCHANGELOG.mdandgit log <latest-release>..HEAD; check coverage of public changes and migration guidance for breaking changes. - Check current versions in
bashunit,package.json,docs/package.json, and both lockfiles (top-level andpackages[""].version). The latest dated changelog section must agree;Unreleaseddescribes the next version. - Run the quality gate in
.agnostic-ai/AGNOSTIC_AI.mdonce. Reuse passing results for unchanged content. Use targeted checks to investigate failures; repeat suites only for new changes or a specific flakiness concern. - Verify CI for the exact current main commit, not a previous run: tests, Bash 3.0 compatibility, build, docs, static analysis and formatting must pass. Check the full OS matrix for changes to paths, permissions or runtime behavior. Use
gh run list --branch mainand inspect each relevant run. - Inspect the changed paths for unsafe input handling, secrets and undocumented public behavior. Use
.agnostic-ai/rules/bash-style.mdandtests/unit/project/bash_compatibility_test.shfor compatibility;[[ ]]is a style choice, not a Bash 3.0 failure. - Check affected README examples and documentation links. If Docker is available and Linux behavior needs local verification, use
make docker/alpineandmake docker/ubuntu; otherwise report the platform coverage supplied by CI. - Smoke-test
./bashunit --help,./bashunit --version, and a single assertion in a unique temporary test file. Clean up that file. - Preview the chosen version with
./release.sh <version> --dry-run. For changes to the release process, also inspect--sandboxoutput and its release commit without publishing.
Report passed checks, failures and specific unverified items. Pending CI is pending, not passed. Stop publishing on failed checks. Do not create tags manually or run the release script in publishing mode from this skill.
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.
- 5d ago Changed · -70 lines c0528e51be51
- 1mo ago First seen · 91 lines · 9 tokens per session scan A 30339dc2f8d0
pre-release is a skill published in the GitHub repository TypedDevs/bashunit (435 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 494 once invoked, about $0.0000 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-30.
Other skills, from other repositories
wispr-flow-debug
Debug and test the Wispr Flow AutoHotkey dictation triggers (Copilot key + extra keys) from WSL by deploying macos.ahk to the Windows Desktop, reloading AutoHotkey, and reading the debug log. Use when an activation/trigger key isn't starting/stopping dictation, when the overlay clicks land wrong, or when verifying a…
implement
Implement a piece of work based on a spec or set of tickets.
model-merging
Merge multiple fine-tuned models using mergekit to combine capabilities without retraining. Use when creating specialized models by blending domain-specific expertise (math + coding + chat), improving performance beyond single models, or experimenting rapidly with model variants. Covers SLERP, TIES-Merging, DARE, Task…
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.