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 aragaobruno/toolbelt --skill unit-test-bootstrappergit clone --depth 1 https://github.com/aragaobruno/toolbeltWrote 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/aragaobruno/toolbelt/unit-test-bootstrapper)<a href="https://agentmods.dev/skills/aragaobruno/toolbelt/unit-test-bootstrapper"><img src="https://agentmods.dev/badge/skills/aragaobruno/toolbelt/unit-test-bootstrapper.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.00036 | $0.00397 |
| Opus 5 | $0.00018 | $0.00198 |
| Sonnet 5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
unit-test-bootstrapper 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 6d 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
🧪 unit-test-bootstrapper
Overview
Writing unit tests is one of the most repetitive parts of software development, yet it is essential to ensure system stability. The unit-test-bootstrapper automatically reads your source files, analyzes the functions and classes, and leverages the Gemini API to produce robust, production-grade test suites:
- Python: Generates assertions and fixtures using
pytest. - JavaScript/TypeScript: Generates tests using
JestorVitest. - The generated tests cover success cases, boundary conditions, edge cases, and error handling.
Quick Start
To generate PyTest assertions for a Python script:
export GEMINI_API_KEY="your-gemini-key"
uv run --with google-genai skills/devops/unit-test-bootstrapper/scripts/bootstrapper.py skills/context/context-compactor/scripts/compactor.py
This will automatically generate a skills/context/context-compactor/scripts/test_compactor.py file.
To specify a custom output path:
uv run --with google-genai skills/devops/unit-test-bootstrapper/scripts/bootstrapper.py src/utils.js --output tests/utils.test.js
Utility Scripts
bootstrapper.py (CLI)
A Python script to generate unit tests.
- Arguments:
<file_path>(required),-o/--output <path>(optional) - Examples:
# Generate test_compactor.py in the same folder as compactor.py python bootstrapper.py compactor.py # Save Jest test to a specific tests folder python bootstrapper.py src/auth.ts -o tests/auth.test.ts
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.
- 6d ago First seen · 42 lines · 36 tokens per session scan A 625af20478f2
unit-test-bootstrapper is a skill published in the GitHub repository aragaobruno/toolbelt (2 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 397 once invoked, about $0.0002 per session on Opus 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
aidex-coverage
Use when writing, placing, or running tests in any project — which layer a behaviour belongs in ("unit or E2E for X", "component test or browser test"), which tests to run for a change instead of the whole suite, when to extract a fixture, setting up an isolated disposable E2E environment, or the per-project testing…
test-software
Design, implement, and evaluate risk-based software tests across unit, integration, contract, end-to-end, and regression layers. Use when adding tests, reproducing bugs, improving coverage, diagnosing flaky tests, or defining a test strategy; do not use to change production behavior unless the user also requests…
sap-abap-change-assurance
Assess an SAP transport before release by running ATC, ABAP Unit, and optional cross-system comparison, then produce JSON, SARIF, and JUnit evidence. Use when reviewing a transport, preparing a release gate, investigating a failed quality gate, or integrating SAP change checks into CI.
test-generator
Generate tests following project patterns — table-driven, edge cases, multi-stack aware.
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.