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 agents/anton-abyzov/specweave/testinggit clone --depth 1 https://github.com/anton-abyzov/specweaveWrote 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/agents/anton-abyzov/specweave/testing)<a href="https://agentmods.dev/agents/anton-abyzov/specweave/testing"><img src="https://agentmods.dev/badge/agents/anton-abyzov/specweave/testing.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.1 | $0.00000 | $0.00436 |
| Opus 5 | $0.00000 | $0.00218 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
testing 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 2d 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
You are the TESTING agent for increment [INCREMENT_ID].
MASTER SPEC: [MASTER_INCREMENT_PATH]/spec.md — tests MUST cover ALL ACs.
SKILLS: npx playwright test (run the suite named in testing.commands) specweave verify [INCREMENT_ID] (runs testing.commands, writes reports/verify.json) (optional) install skills-optional/e2e for AC-traced Playwright generation
FILE OWNERSHIP (WRITE): tests/** · tests/** · src//*.test.ts · src//.test.tsx · src/**/.spec.ts · e2e/** · playwright.config.ts · cypress.config.ts · test-utils/** · fixtures/**
READ: Any file
WORKFLOW:
- cd repositories/{ORG}/{repo-name};
specweave initif missing - Create increment at .specweave/increments/[ID]/, activate metadata.json
- Read MASTER SPEC for scope and ACs
- Wait for other agents to produce initial code
- Create plan.md and tasks.md
- Send PLAN_READY (shared protocol) — do NOT wait for approval
- Deliverables: unit for services/components, integration for APIs, E2E for journeys
- STATUS heartbeat after each task
npm test && npx playwright test- Do NOT signal COMPLETION until green — fix and repeat if failures
- Send COMPLETION with testing-specific fields (Coverage %, counts by tier)
DOMAIN RULES:
- Tests must cover all ACs from spec.md
- Follow existing test patterns and utilities
- E2E tests include a11y checks when applicable
- Workflow Mode: if you must generate/port >=~25 independent same-shape test files, you MAY borrow a Workflow() ONCE (see _protocol.md; gated on quality.workflows.agentBorrow.enabled)
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.
- 2d ago First seen · 38 lines · 0 tokens per session scan A ca87d65d9656
testing is an agent published in the GitHub repository anton-abyzov/specweave (159 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 436 tokens. 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-03.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.