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/firstp1ck/pi-coding-agent-forge/test-plan-generatornpx skills add Firstp1ck/pi-coding-agent-forge --skill test-plan-generatorgit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forgeWhat 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.00051 | $0.00733 |
| Opus 5 | $0.00026 | $0.00367 |
| Sonnet 5 | $0.00010 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
test-plan-generator 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Plan Generator
Generate structured, prioritized test plans from spec and architecture documents.
Inputs
projects/<project-name>/combined-plan.md(primary source of truth)projects/<project-name>/spec.md(original requirements)projects/<project-name>/architecture.md(module boundaries and interfaces)- Forge's completion report (existing test coverage)
Process
Step 1 — Extract Requirements
Read the combined plan and extract every testable requirement:
- Explicit acceptance criteria from the spec
- Interface contracts from the architecture
- Security constraints from Zero's review
- Error handling expectations
- Edge cases mentioned in the spec
- Non-functional requirements (performance, accessibility)
Step 2 — Derive Test Cases
For each requirement, create one or more test cases:
| ID | Requirement | Test Case | Category | Priority | Status |
|---|---|---|---|---|---|
| TC-001 | User can create account | Valid email + password creates account | E2E | P0 | Pending |
| TC-002 | User can create account | Duplicate email rejected with error | E2E | P0 | Pending |
| TC-003 | Email validation | Invalid format "foo@" rejected | Unit | P1 | Pending |
| TC-004 | Rate limit on login | 6th attempt within 1 min returns 429 | Integration | P1 | Pending |
Step 3 — Prioritize
Use this priority scheme:
| Priority | Criteria | Examples |
|---|---|---|
| P0 (Must test) | Core user flows, data integrity, auth | Login, create, read, update, delete |
| P1 (Should test) | Error handling, edge cases, security functional | Invalid input, rate limits, empty states |
| P2 (Nice to test) | Boundary values, concurrent access, rare paths | Max-length input, simultaneous edits |
| P3 (If time allows) | Cosmetic, UX polish, accessibility | Layout consistency, keyboard navigation |
Step 4 — Coverage Analysis
Compare test cases against spec requirements:
## Coverage Matrix
| Spec Section | Requirements | Test Cases | Coverage |
|---|---|---|---|
| Authentication | 5 | 12 | 100% |
| User Profile | 3 | 6 | 100% |
| Data Export | 2 | 1 | 50% — missing error path tests |
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 · 104 lines · 51 tokens per session scan A 98b02ba205ca
test-plan-generator is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (74 stars, last pushed 3d ago), licensed MIT. It adds 51 tokens to every session and 733 once invoked, about $0.0003 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
mandu-testing
Testing patterns for Mandu applications. Use when writing unit tests, integration tests, or E2E tests. Triggers on test, spec, Bun test, Playwright, or testing tasks.
testing-automation-expert
Production-grade testing strategies for robust, maintainable systems. Covers unit/integration/E2E testing, contract testing, accessibility, mutation testing, and CI/CD patterns. Supports Python (pytest) and TypeScript (Jest/Vitest/Playwright).
testing-patterns
Testing patterns and principles. Unit, integration, mocking strategies.
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…
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
Run tests. Use after code changes to validate. Arguments: unit (default, no GPU), e2e (with models), filter name, or all.