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 agentmods add skills/bugrabilge/bilge-development-kit/testnpx skills add bugrabilge/bilge-development-kit --skill testgit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWhat 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 | $0.00039 | $0.00681 |
| Opus 5 | $0.00019 | $0.00341 |
| Sonnet 5 | $0.00008 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
test 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/test - Test Generation and Execution
$ARGUMENTS
Purpose
This command generates tests, runs existing tests, or checks test coverage.
Sub-commands
/test - Run all tests
/test [file/feature] - Generate tests for specific target
/test coverage - Show test coverage report
/test watch - Run tests in watch mode
Behavior
Generate Tests
When asked to test a file or feature:
-
Analyze the code
- Identify functions and methods
- Find edge cases
- Detect dependencies to mock
-
Generate test cases
- Happy path tests
- Error cases
- Edge cases
- Integration tests (if needed)
-
Write tests
- Use project's test framework (Jest, Vitest, etc.)
- Follow existing test patterns
- Mock external dependencies
Output Format
For Test Generation
## 🧪 Tests: [Target]
### Test Plan
| Test Case | Type | Coverage |
|-----------|------|----------|
| Should create user | Unit | Happy path |
| Should reject invalid email | Unit | Validation |
| Should handle db error | Unit | Error case |
### Generated Tests
`tests/[file].test.ts`
[Code block with tests]
---
Run with: `npm test`
For Test Execution
🧪 Running tests...
✅ auth.test.ts (5 passed)
✅ user.test.ts (8 passed)
❌ order.test.ts (2 passed, 1 failed)
Failed:
✗ should calculate total with discount
Expected: 90
Received: 100
Total: 15 tests (14 passed, 1 failed)
Examples
/test src/services/auth.service.ts
/test user registration flow
/test coverage
/test fix failed tests
Test Patterns
Unit Test Structure
describe('AuthService', () => {
describe('login', () => {
it('should return token for valid credentials', async () => {
// Arrange
const credentials = { email: '[email protected]', password: 'pass123' };
// Act
const result = await authService.login(credentials);
// Assert
expect(result.token).toBeDefined();
});
it('should throw for invalid password', async () => {
// Arrange
const credentials = { email: '[email protected]', password: 'wrong' };
// Act & Assert
await expect(authService.login(credentials)).rejects.toThrow('Invalid credentials');
});
});
});
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.
- 2d ago First seen · 152 lines · 39 tokens per session scan A 0b67193bb090
test is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 681 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…