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 commitgit 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/commit)<a href="https://agentmods.dev/skills/typeddevs/bashunit/commit"><img src="https://agentmods.dev/badge/skills/typeddevs/bashunit/commit/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/commit"><img src="https://agentmods.dev/badge/skills/typeddevs/bashunit/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00010 | $0.00425 |
| Opus 5.5 | $0.00004 | $0.00170 |
| Sonnet 5.5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
commit 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
Commit
Use this skill for project commits. Read formatting constraints when checking shell changes; repository paths are relative to the repository root. Accept an optional message hint.
- Inspect
git status --short, the current branch, relevant staged and unstaged diffs, and recent history. Reuse state already obtained during this task unless it may have changed. Understand the complete change and confirm the coordinator's canonical quality gate passed after the final edits; do not repeat a passing gate without new changes or unresolved evidence. - Stage only the relevant files by explicit name. Never use
git add .orgit add -A, and keep credentials out of Git. Reviewgit diff --cachedbefore committing; one commit covers one logical change. - Use
<type>(<optional-scope>): <description>with the project's types:feat,fix,perf,docs,style,refactor,test, orchore. Choose a domain scope such asassert,runner,cli,doubles,docs, orciwhen useful. Follow sibling history, use a lowercase imperative subject under 70 characters without a final period, and add a body only when the reason needs explanation. - Use the configured Git identity and
git commitwith the exact message. Write public text in the user's voice without attribution; tooling names are appropriate when tooling is the subject. Never skip hooks or amend published history. If a hook fails, fix the cause and retry a new commit rather than rewriting an existing one. - Verify the created commit with
git log --oneline -1and inspect the remaining working state. A commit does not grant push authorization; use theprskill for an authorized PR delivery.
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.
- 5d ago Changed · -73 lines 6ebeaba9d255
- 1mo ago First seen · 92 lines · 10 tokens per session scan A e46981e16b2a
commit is a skill published in the GitHub repository TypedDevs/bashunit (435 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 425 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.