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 nikeyes/stepwise-dev --skill bugmagnetgit clone --depth 1 https://github.com/nikeyes/stepwise-devWrote 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/nikeyes/stepwise-dev/bugmagnet)<a href="https://agentmods.dev/skills/nikeyes/stepwise-dev/bugmagnet"><img src="https://agentmods.dev/badge/skills/nikeyes/stepwise-dev/bugmagnet/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/nikeyes/stepwise-dev/bugmagnet"><img src="https://agentmods.dev/badge/skills/nikeyes/stepwise-dev/bugmagnet.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.00076 | $0.00506 |
| Opus 5.5 | $0.00030 | $0.00202 |
| Sonnet 5.5 | $0.00015 | $0.00101 |
| Haiku 4.5 | $0.00008 | $0.00051 |
Grade A, and why
bugmagnet 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 1mo 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
BugMagnet
Analyze a code module, write comprehensive edge-case tests, and document discovered bugs.
Attribution: Adapted from BugMagnet AI Assistant by Gojko Adzic (MIT License).
Usage
/bugmagnet <implementation-file-path>
Workflow
- Read the implementation file and its existing tests
- Identify untested edge cases, boundary conditions, and error paths
- Write tests — run each one immediately after writing
- When a test reveals a bug, document it as a skipped test (see format below), then explore nearby: bugs cluster together
- Summarize findings
Do NOT modify the implementation file. Only write tests.
Bug Documentation Format
When a test reveals unexpected behavior, create a skipped test using the framework's skip mechanism with "- BUG" in the test name:
test.skip('normalizeEmail crashes on input without @ - BUG', () => {
/*
* ROOT CAUSE: destructuring email.split("@") fails when no @ present
* CODE LOCATION: src/validator.ts:49
* PROPOSED FIX: guard with if (!email.includes("@")) before split
* EXPECTED: throws or returns input unchanged
* ACTUAL: TypeError: Cannot read properties of undefined
*/
expect(() => normalizeEmail("nodomain")).not.toThrow();
});
Every skipped BUG test must include: ROOT CAUSE, CODE LOCATION, PROPOSED FIX, EXPECTED vs ACTUAL.
Summary Format
After all tests are written, provide:
## Test Coverage Summary
**Tests Added:** N total
- Category 1 (X tests)
- Category 2 (Y tests)
**Results:** X passing, Y skipped (bugs)
**Bugs Discovered:**
1. Bug name — file:line
- Root cause: ...
- Proposed fix: ...
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.
- 1mo ago First seen · 64 lines · 76 tokens per session scan A bdd11a799390
bugmagnet is a skill published in the GitHub repository nikeyes/stepwise-dev (24 stars, last pushed 6d ago), licensed Apache-2.0. It adds 76 tokens to every session and 506 once invoked, about $0.0003 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
test-review
You are an expert DataHub test reviewer. Your role is to evaluate pytest smoke tests against established testing standards, identify issues, and provide actionable feedback.
grade-tests
Grade curated individual tests for readiness, A-F quality and improvements. ALWAYS USE FOR: grade tests, review only a named test, per-test readiness or quality bands for supplied methods, bodies, file spans or bounded PR diffs, including existing tests. Return Pass/Failed/Uncertain/Not applicable; unresolved/empty…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…
dart-mechanical-refactor
DART Mechanical Refactor: perform a behavior-preserving mechanical refactor.
quality-checklist
Validate implementation quality through custom checklists, scoring against constitution standards, specification coverage, and producing remediation recommendations.