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 athola/skrills --skill test-writergit clone --depth 1 https://github.com/athola/skrillsWrote 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/athola/skrills/test-writer)<a href="https://agentmods.dev/skills/athola/skrills/test-writer"><img src="https://agentmods.dev/badge/skills/athola/skrills/test-writer/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/athola/skrills/test-writer"><img src="https://agentmods.dev/badge/skills/athola/skrills/test-writer.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.00014 | $0.00179 |
| Opus 5 | $0.00007 | $0.00089 |
| Sonnet 5 | $0.00003 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
test-writer 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 10d 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
Test Writer
Expert at writing tests that ensure code quality and prevent regressions.
Test Types
- Unit Tests: Test individual functions in isolation
- Integration Tests: Test component interactions
- E2E Tests: Test complete user workflows
Testing Principles
- Arrange, Act, Assert (AAA) pattern
- One assertion per test when practical
- Test edge cases and error conditions
- Use meaningful test descriptions
Coverage Guidelines
- Aim for meaningful coverage, not just high percentages
- Focus on critical paths and business logic
- Test both happy paths and error scenarios
- Include boundary value tests
Mocking Strategy
- Mock external dependencies
- Use dependency injection for testability
- Avoid over-mocking internal implementation
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.
- 10d ago First seen · 31 lines · 14 tokens per session scan A de6120424a85
test-writer is a skill published in the GitHub repository athola/skrills (69 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 179 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-08-30.
Other skills, from other repositories
smoke-test
Launch the app and hands-on verify that it works by interacting with it. Falls back to an existing integration test suite when there is no interactive surface in scope. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does…
tdd-workflow
A test-first development workflow, commonly called TDD, where a failing test is written before the code that should make it pass. The cycle then adds the smallest working change and cleans it up.
e2e-playwright
Use when writing end-to-end browser tests with Playwright. Covers resilient locators, auto-waiting, network interception, authentication reuse, parallelization, and eliminating flakiness.
test-strategy
Use when deciding what to test and at which level. Covers the test pyramid, what belongs in unit versus integration versus end-to-end tests, coverage as a signal rather than a target, and eliminating flakiness.
web-app-testing
Use when testing a web application interactively — verifying a feature, reproducing a bug, or checking a flow in a real browser. Covers systematic exploration, console and network inspection, and reporting what you find.
visual-qa
Use when verifying that a UI renders correctly. Covers visual regression testing, responsive checks across breakpoints, cross-browser verification, and screenshot-based review of an implementation against a design.