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 prgit 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/pr)<a href="https://agentmods.dev/skills/typeddevs/bashunit/pr"><img src="https://agentmods.dev/badge/skills/typeddevs/bashunit/pr/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/pr"><img src="https://agentmods.dev/badge/skills/typeddevs/bashunit/pr.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.00016 | $0.00461 |
| Opus 5.5 | $0.00006 | $0.00184 |
| Sonnet 5.5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
pr 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
Create a pull request
Use this skill for PR creation. Repository paths are relative to the repository root.
- Inspect the current branch,
git status --short,git log main..HEAD --oneline, andgit diff main..HEAD --stat. Keep the user's edits and scope. - Verify
CHANGELOG.mddescribes public behavior changes underUnreleased, with issue references where applicable. Contributor-only changes can update the existing contributor entry; do not add a self-referential changelog note for a changelog edit. - Complete the quality gate and commit workflow in
.agnostic-ai/AGNOSTIC_AI.mdand {{$SKILL:commit}}. Reuse passing checks for unchanged content. Do not rely on an optional Git hook being installed. Obtain the required diff review before pushing. - Push with
git push -u origin HEADwhen authorized. If it fails, diagnose and fix the cause; never bypass hooks or branch protection. - Read
.github/PULL_REQUEST_TEMPLATE.mdand follow its current headings and checklist. Use a conventional title under 70 characters. Link an actual issue withRelated #N, never invent one. Explain the problem and resulting behavior in 1-2 background sentences and 2-4 change bullets, including concise validation. Avoid file inventories and conversational history. - Write the exact PR body to a temporary file; create with
gh pr create --title <title> --assignee @me --label <label> --body-file <file>. Select one label:bug,enhancement,documentation,refactor,ui, orinvestigation, according to the change. Report the URL. - If an issue has a configured project in
.agnostic-ai/local/github-project.json, use its actual IDs to move the issue to In Review. Do not assume project access or invent a missing configuration; report an unavailable update separately.
Respect existing publishing authorization. Creating a PR does not authorize merging it.
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 · -89 lines 0ed6ffe7d218
- 1mo ago First seen · 111 lines · 16 tokens per session scan A 09602d0a057e
pr is a skill published in the GitHub repository TypedDevs/bashunit (435 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 461 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-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.