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 TheBeardedBearSAS/claude-craft --skill testing-pythongit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/testing-python)<a href="https://agentmods.dev/skills/thebeardedbearsas/claude-craft/testing-python"><img src="https://agentmods.dev/badge/skills/thebeardedbearsas/claude-craft/testing-python/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/thebeardedbearsas/claude-craft/testing-python"><img src="https://agentmods.dev/badge/skills/thebeardedbearsas/claude-craft/testing-python.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00028 | $0.00563 |
| Opus 5.5 | $0.00011 | $0.00225 |
| Sonnet 5.5 | $0.00006 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
testing-python 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 5d 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
Stratégie de Tests Python 3.14+
Versions : Python 3.14+ | pytest 9.x | Ruff 0.17+ | mypy 2.x | Playwright
Ruff remplace Black + isort + Flake8 (10-100x plus rapide). mypy strict élimine les bugs de type à la compilation.
Stack recommandée 2026
| Type | Outil | Usage |
|---|---|---|
| Unit/Integration | pytest 9.x | Tests backend FastAPI/Django |
| Linting + Format | Ruff 0.17+ | 10-100× plus rapide que Black+Flake8 |
| Type checking | mypy 2.x strict | Vérification statique |
| E2E/Browser | Playwright | Tests frontend web |
| BDD (Gherkin) | pytest-bdd | Scénarios Given/When/Then |
| Mutation | Mutmut | Qualité des tests (score >= 80%) |
| Property-based | Hypothesis | Génération de cas de test automatique |
Sources : pytest, Ruff, Mutmut
Invariants non-négociables
- Couverture >= 80% (
--cov-fail-under=80danspyproject.toml) - mypy strict — zéro
Anynon justifié,disallow_untyped_defs = true - Ruff obligatoire (check + format) dans CI
- Pattern AAA (Arrange-Act-Assert) dans chaque test
- Fixtures pytest pour l'injection de dépendances (pas d'état global)
- Mutation score >= 80% via Mutmut
Checklist par type
| Type | Vérification |
|---|---|
| Unit | Isolation totale, fixtures pytest, mocks unittest.mock |
| Integration | TestClient FastAPI / Client Django, DB de test |
| E2E | Playwright sync_api, expect() assertions |
| Property | Hypothesis @given pour edge cases automatiques |
| Mutation | mutmut run, score >= 80 avant merge |
Détails complets, exemples de code, configs et checklists : voir REFERENCE.md
What ships with it
1 file 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.
- 5d ago Changed · +1 lines 1883f83a4e39
- 1mo ago First seen · 46 lines · 28 tokens per session scan A 98539115a2be
testing-python is a skill published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 563 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-09-03.
Other skills, from other repositories
test-execution
Run unit and integration tests, generate coverage reports, and view results. Use to validate code changes before committing or merging.
javascript-testing-patterns
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
adk-verify-snippets
Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail report with per-snippet coverage. Use when the user asks to verify, test, or validate the code samples in a README, a guide…
adk-setup
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test run. Runs only when explicitly requested, never on its own. Use when asked to set up, bootstrap, or repair a development…
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
qa/test-strategy
A testing strategy based on the testing pyramid: many small unit tests, fewer integration tests, and a smaller set of end-to-end tests that follow real user journeys. It also defines checks for security, boundaries, permissions, and business consistency.