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 gul-labs/craftsman-marketplace --skill craft-testinggit clone --depth 1 https://github.com/gul-labs/craftsman-marketplaceWrote 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/gul-labs/craftsman-marketplace/craft-testing)<a href="https://agentmods.dev/skills/gul-labs/craftsman-marketplace/craft-testing"><img src="https://agentmods.dev/badge/skills/gul-labs/craftsman-marketplace/craft-testing/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/gul-labs/craftsman-marketplace/craft-testing"><img src="https://agentmods.dev/badge/skills/gul-labs/craftsman-marketplace/craft-testing.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.00162 | $0.03396 |
| Opus 5.5 | $0.00065 | $0.01358 |
| Sonnet 5.5 | $0.00032 | $0.00679 |
| Haiku 4.5 | $0.00016 | $0.00340 |
Grade A, and why
craft-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 1mo 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Craft
This skill encodes one engineer's standard for testing software so the suite is actually trusted — fast, deterministic, and catching real regressions rather than decorating the coverage badge. The method and opinions live here; the project specifics (test runner, framework, what's already covered) live in the target repo — always discover them, never assume or hardcode.
The persona this serves usually arrives at one of two extremes: no tests at all, or a pile of AI-generated tests that don't test anything — they assert that a mock was called, pin implementation details, or cover trivial getters to hit a number while the payment path has zero coverage. Both feel like "we have testing." Neither catches the bug that takes the app down. The job is to move them to a small set of tests they can trust, on the paths that actually matter.
Operating principle — discover before you build
Different repos already have different pieces in place. Before adding anything, map what exists so you extend rather than duplicate or fight it:
package.json/ lockfile → test runner (vitest,jest,playwright,@testing-library/*,pytest),test/test:e2e/coveragescripts, and whether tests even run. Coverage tooling or a configured percentage is context, not proof that the tests are adequate.- Test config (
vitest.config.*,jest.config.*,playwright.config.*,pytest.ini,conftest.py) → environment, setup files, coverage thresholds already set. - Existing tests (
*.test.*,*.spec.*,__tests__/,e2e/,tests/) → conventions, what's covered, and the quality of what's there (real assertions vs. tautologies — read a few). - Read CI config files (
package.jsonscripts,.github/workflows) — read-only context for understanding which suites currently gate a merge; wiring changes → craft-infra.
State what you found — including "the tests that exist don't assert anything real" — then propose the smallest set of additions that closes the gap on the paths that matter.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +9 lines 1854263c41d3
- 1mo ago First seen · 201 lines · 162 tokens per session scan A dc5fbedc93b1
craft-testing is a skill published in the GitHub repository gul-labs/craftsman-marketplace (1 stars, last pushed 5d ago), licensed MIT. It adds 162 tokens to every session and 3,396 once invoked, about $0.0006 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-strategy-document
Create a production-ready Testing Strategy and QA Execution Plan. Covers testing levels (unit, integration, E2E, performance), mocking boundaries, test environment matrix, code coverage thresholds, and automated CI pipeline runsheets. Use when establishing a QA framework for a new system or feature set.
test-audit
Batch audit of test files against Q1-Q25 quality gates and AP1-AP32 anti-patterns. Detects orphan tests, phantom mocks, untested public methods. Tiered output (A/B/C/D) with critical gate enforcement and optional post-audit fix workflow. Flags: zuvo:test-audit all | [path] | [file] | --deep | --quick | --include-e2e |…
test-selection
Use this skill when someone describes a specific code path, feature, or bug and asks what kind of test to write for it — or when an audit or strategy engagement surfaces a testing gap and needs a recommendation for where to start. Trigger on "what test should I write for this", "unit or integration test for X", "our…
seams
Use when you want to unit-test logic but can't without a database, network, clock, or a pile of mocks — or when a function fetches, computes, branches on policy, and writes all in one breath. Splits the decision (pure logic) from the action (I/O and side effects) along the natural seam, so the logic becomes testable…
pwp-test
Testing strategy and implementation protocol — structured quality assurance that catches real bugs. Use this skill whenever the user asks to write tests, add test coverage, set up a testing strategy, or asks 'how should I test this'. Also use when they say 'add tests', 'write tests for this', 'test coverage', 'what…
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…