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/pilotspace/pilot-space/write-testsnpx skills add pilotspace/pilot-space --skill write-testsgit clone --depth 1 https://github.com/pilotspace/pilot-spaceWhat 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.00021 | $0.01338 |
| Opus 5 | $0.00010 | $0.00669 |
| Sonnet 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 yesterday.
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.
- yesterday 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 2mo 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. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.