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 pilotspace/pilot-space --skill write-testsgit clone --depth 1 https://github.com/pilotspace/pilot-spaceWrote 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/pilotspace/pilot-space/write-tests)<a href="https://agentmods.dev/skills/pilotspace/pilot-space/write-tests"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/write-tests/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/pilotspace/pilot-space/write-tests"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/write-tests.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.00021 | $0.01338 |
| Opus 5.5 | $0.00008 | $0.00535 |
| Sonnet 5.5 | $0.00004 | $0.00268 |
| Haiku 4.5 | $0.00002 | $0.00134 |
Grade A, and why
write-tests 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 2mo 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Tests Skill
Generate unit tests, integration tests, or end-to-end tests for existing code. Analyzes code structure to produce comprehensive test coverage including happy paths, edge cases, and error scenarios.
Quick Start
Use this skill when:
- User requests test generation (
/write-tests) - Agent detects low coverage for a code block
- User pastes code and asks for tests
Example:
User: "Write tests for the InvitationService.execute method"
AI generates:
- Unit test: happy path — valid invitation created
- Unit test: duplicate email raises ValueError
- Unit test: invalid role raises ValidationError
- Integration test: full create → email dispatch → DB persist flow
Workflow
-
Analyze Target Code
- Read note content for the code to be tested
- Search for existing test files via
search_note_content - Identify: public API surface, dependencies, invariants, error paths
-
Determine Test Strategy
- Unit tests: mock all external dependencies (repos, queues, email)
- Integration tests: use real DB session, mock only external APIs
- Coverage target: >80% per project standard
-
Generate Tests
- Framework:
pytest+pytest-asynciofor async (backend),vitestfor frontend - Use
AsyncMockfor async repo/service dependencies - Follow AAA pattern: Arrange → Act → Assert
- Cover: happy path, at least 2 edge cases, error/exception paths
- No placeholders — all
assertstatements must have concrete expected values
- Framework:
-
Insert to Note
- Use
insert_blockto add test code blocks after the existing code in the note - Prepend with
## Generated Tests: <ClassName>heading - Include file path comment at top of block
- Use
-
Return Suggestion Status
- Return
status: pending_suggestion— user reviews before copying to test file - Include coverage estimate in summary
- Return
Output Format
{
"status": "pending_suggestion",
"skill": "write-tests",
"blocks_inserted": 2,
"note_id": "note-uuid",
"summary": "Generated 8 unit tests + 2 integration tests for InvitationService",
"estimated_coverage": "92%",
"test_file_path": "backend/tests/unit/services/test_invitation_service.py"
}
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.
- 2mo ago First seen · 178 lines · 21 tokens per session scan A f0b6444c2557
write-tests is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,338 once invoked, about $0.0001 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-31.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
test-automation-expert
Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.