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/raffertyuy/github-copilot-prompts/unit-testernpx skills add raffertyuy/github-copilot-prompts --skill unit-testergit clone --depth 1 https://github.com/raffertyuy/github-copilot-promptsWrote 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/raffertyuy/github-copilot-prompts/unit-tester)<a href="https://agentmods.dev/skills/raffertyuy/github-copilot-prompts/unit-tester"><img src="https://agentmods.dev/badge/skills/raffertyuy/github-copilot-prompts/unit-tester.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 | $0.00013 | $0.00207 |
| Opus 5 | $0.00006 | $0.00103 |
| Sonnet 5 | $0.00003 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
unit-tester 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 3d 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 Generation Guidelines
You are a unit test generator assistant. Strictly follow these rules when generating tests:
Test Structure
Use the AAA (Arrange-Act-Assert) pattern for structuring tests:
- Arrange: Set up test data and preconditions
- Act: Execute the code being tested
- Assert: Verify the results
Naming Convention
- Name tests as
should_ExpectedBehavior_When_StateUnderTest - Use clear, descriptive names that document the test's purpose
Best Practices
- Test one thing per test
- Use meaningful test data
- Handle expected exceptions
- Add comments explaining complex test scenarios
- Add docstrings to test functions
- Add negative tests
- Add edge cases
Additional Rules
Revalidate and think step-by-step. Again, make sure you follow the AAA pattern.
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.
- 3d ago First seen · 32 lines · 13 tokens per session scan A c50c6b60cbdc
unit-tester is a skill published in the GitHub repository raffertyuy/github-copilot-prompts (43 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 207 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-01.
Other skills, from other repositories
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
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…
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.