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 secondsky/claude-skills --skill bun-test-lifecyclegit clone --depth 1 https://github.com/secondsky/claude-skillsWrote 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/secondsky/claude-skills/bun-test-lifecycle)<a href="https://agentmods.dev/skills/secondsky/claude-skills/bun-test-lifecycle"><img src="https://agentmods.dev/badge/skills/secondsky/claude-skills/bun-test-lifecycle.svg" alt="Measured on agentmods" 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 Memory Poisoning · line 178 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00027 | $0.01435 |
| Opus 5 | $0.00014 | $0.00718 |
| Sonnet 5 | $0.00005 | $0.00287 |
| Haiku 4.5 | $0.00003 | $0.00144 |
Grade A, and why
bun-test-lifecycle 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.
How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bun Test Lifecycle
Bun supports Jest-compatible lifecycle hooks for test setup and teardown.
Lifecycle Hooks
import { test, expect, beforeAll, afterAll, beforeEach, afterEach } from "bun:test";
let db: Database;
let testData: any;
// Runs once before all tests in file
beforeAll(async () => {
db = await Database.connect();
});
// Runs once after all tests in file
afterAll(async () => {
await db.close();
});
// Runs before each test
beforeEach(() => {
testData = { id: 1, name: "test" };
});
// Runs after each test
afterEach(() => {
testData = null;
});
test("example", () => {
expect(testData.name).toBe("test");
});
Hook Execution Order
beforeAll
├── beforeEach
│ └── test 1
│ └── afterEach
├── beforeEach
│ └── test 2
│ └── afterEach
afterAll
Nested Describe Hooks
import { describe, test, beforeAll, beforeEach, afterEach, afterAll } from "bun:test";
describe("outer", () => {
beforeAll(() => console.log("1. outer beforeAll"));
afterAll(() => console.log("6. outer afterAll"));
beforeEach(() => console.log("2. outer beforeEach"));
afterEach(() => console.log("5. outer afterEach"));
describe("inner", () => {
beforeEach(() => console.log("3. inner beforeEach"));
afterEach(() => console.log("4. inner afterEach"));
test("test", () => {
console.log("test runs here");
});
});
});
// Output:
// 1. outer beforeAll
// 2. outer beforeEach
// 3. inner beforeEach
// test runs here
// 4. inner afterEach
// 5. outer afterEach
// 6. outer afterAll
Async Hooks
beforeAll(async () => {
await setupDatabase();
});
beforeEach(async () => {
await seedTestData();
});
afterEach(async () => {
await clearTestData();
});
afterAll(async () => {
await teardownDatabase();
});
Timeout for Hooks
// Set timeout for slow setup
beforeAll(async () => {
await slowSetup();
}, 30000); // 30 seconds
Preload Scripts
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 First seen · 307 lines · 27 tokens per session scan A 70111d8d38fb
bun-test-lifecycle is a skill published in the GitHub repository secondsky/claude-skills (215 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,435 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
dotnet-test
This skill should be used when running .NET tests selectively with a build-first, test-targeted workflow. Use it for running tests with xUnit focus.
remember
Record why something is the way it is — a decision and its reasoning, a lesson that cost time, or a standing constraint. Use when the reasoning behind a choice would be expensive to reconstruct later.
bootstrap
Set up chamnan in this repository for the first time — build the architecture index, measure how well the code describes itself, fill in missing file comments, and record a baseline. Run once per repo.
resume
Write down where this stretch of work stopped, so the next session continues instead of restarting. Use at the end of a working session, or when handing the repository to someone else.
milestone
Record a change that reshaped the repository — what moved, why it was worth doing, and which areas it touched. Use after a migration, a rewrite, or a decision that changed how part of the system works.
capture
Write down a procedure worth keeping — a multi-step process, a trap that cost real time, or something that has now come up three times. Use it the moment you finish such a task, while the details are still exact.