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 srnichols/plan-forge --skill test-sweepgit clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/srnichols/plan-forge/test-sweep)<a href="https://agentmods.dev/skills/srnichols/plan-forge/test-sweep"><img src="https://agentmods.dev/badge/skills/srnichols/plan-forge/test-sweep/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/srnichols/plan-forge/test-sweep"><img src="https://agentmods.dev/badge/skills/srnichols/plan-forge/test-sweep.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.00878 |
| Opus 5.5 | $0.00015 | $0.00351 |
| Sonnet 5.5 | $0.00008 | $0.00176 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
test-sweep 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Sweep Skill
Trigger
"Run all tests" / "Full test sweep" / "Check test health"
Steps
1. Unit Tests
dotnet test --filter "Category=Unit" --logger "console;verbosity=normal" --results-directory TestResults/
Conditional: Unit Test Failure
If unit tests fail → skip integration/E2E tests, go directly to Report.
2. Integration Tests
dotnet test --filter "Category=Integration" --logger "console;verbosity=normal" --results-directory TestResults/
3. API / GraphQL Tests
dotnet test --filter "Category=Api|Category=GraphQL" --logger "console;verbosity=normal" --results-directory TestResults/
4. E2E Tests (if available)
dotnet test --filter "Category=E2E" --logger "console;verbosity=normal" --results-directory TestResults/
5. Completeness Scan
Use the forge_sweep MCP tool to scan for TODO/FIXME/stub markers in the codebase.
6. Report
Aggregate results:
✅ Unit: X passed, Y failed, Z skipped
✅ Integration: X passed, Y failed, Z skipped
✅ API: X passed, Y failed, Z skipped
✅ E2E: X passed, Y failed, Z skipped
✅ Sweep: N markers (TODO/FIXME/stub)
──────────────────────────────────────────────
Total: X passed, Y failed, Z skipped
On Failure
- Show failed test names and error messages
- Read the failing test source to diagnose
- Suggest fixes (ask before applying)
Temper Guards
| Shortcut | Why It Breaks |
|---|---|
| "Skipped tests are probably flaky" | Skipped tests hide real regressions. Each skip needs a documented reason and a linked issue. |
| "80% coverage is good enough" | Coverage thresholds prevent ratcheting down. If baseline is 85%, dropping to 80% means new code is untested. |
| "Integration tests cover the unit tests" | Integration tests are slow and brittle. Unit tests catch logic errors in milliseconds, not minutes. |
| "I'll fix the failing test later" | Broken tests normalize failure. The suite must be green before any code ships. |
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 · 88 lines · 38 tokens per session scan A 75eb90ca5c05
test-sweep is a skill published in the GitHub repository srnichols/plan-forge (6 stars, last pushed 7d ago), licensed MIT. It adds 38 tokens to every session and 878 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
crap-score
Calculates CRAP (Change Risk Anti-Patterns) for a named .NET method, class, or file. USE FOR: explicit CRAP calculation or coverage-and-complexity risk within that named target, including which tests to prioritize. DO NOT USE FOR: project-wide coverage/CRAP, plateaus, or project-wide blockers/priorities…
nunit
Write, run, or repair .NET tests that use NUnit. Use when a repo uses NUnit, [Test], [TestCase], [TestFixture], or NUnit3TestAdapter for VSTest or Microsoft.Testing.Platform execution. USE FOR: writing or reviewing NUnit tests; using [Test], [TestCase], [TestFixture], [SetUp], [TearDown] attributes; configuring…
playwright-visual-testing
Add, repair, or review Playwright visual regression tests for browser-facing .NET apps, including screenshot baselines, Pixelmatch thresholds, deterministic rendering, and GitHub Actions artifacts. USE FOR: toHaveScreenshot, page.screenshot visual checks, Pixelmatch/pngjs comparison scripts, visual baseline updates…
diagnostics-mcp
Use dotnet-diagnostics-mcp for MCP-driven .NET CPU, allocation, GC, and test-host profiling. USE FOR: profiling unit tests or investigating runtime bottlenecks. DO NOT USE FOR: writing test assertions, coverage collection, or precise microbenchmark timing. INVOKES: connect the MCP server, select target processes…
coverlet
Use the open-source free coverlet toolchain for .NET code coverage. Use when a repo needs line and branch coverage, collector versus MSBuild driver selection, or CI-safe coverage commands. USE FOR: coverlet setup; CI line or branch coverage; choosing between collector and MSBuild drivers. DO NOT USE FOR: coverage…