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/vikasudasi/skill-vault/pytest-testingnpx skills add vikasudasi/skill-vault --skill pytest-testinggit clone --depth 1 https://github.com/vikasudasi/skill-vaultWrote 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/vikasudasi/skill-vault/pytest-testing)<a href="https://agentmods.dev/skills/vikasudasi/skill-vault/pytest-testing"><img src="https://agentmods.dev/badge/skills/vikasudasi/skill-vault/pytest-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 | $0.00030 | $0.00995 |
| Opus 5 | $0.00015 | $0.00498 |
| Sonnet 5 | $0.00006 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
pytest-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 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pragmatic pytest
Use when writing or extending a Python test suite — unit tests, fixtures, and a layout that runs cleanly in CI without cross-test contamination.
Layout
tests/
conftest.py # shared fixtures/autouse
fixtures/ # generator helpers (signing, fake stores)
test_x.py # one module per area
Put shared fixtures in conftest.py; keep per-test helpers beside the test that
uses them. A flat tests/ next to the app package beats a nested mirror.
Fixtures and scope
Fixtures are dependency-injected via the parameter name. Scope controls how often the setup runs:
| scope | runs once per | use for |
|---|---|---|
| function | test (default) | most things, isolation |
| class | test class | class-level setup |
| module | test module | expensive per-module resources |
| session | whole run | DB connection, embedder |
import pytest
@pytest.fixture(scope="function")
def db(tmp_path):
conn = connect(str(tmp_path / "app.db"))
yield conn
conn.close()
A fixture that yields gets teardown after the test — prefer yield over
returning, so cleanup runs even on assertion failure.
tmp_path and monkeypatch
tmp_pathis a freshPathper test — never hardcode temp dirs.tmp_path / "app.db"gives each test an isolated DB (Skill Vault does exactly this in its seed tests —connect(str(tmp_path / "app.db"))).monkeypatch.setattr(module, "attr", value)patches for one test and restores automatically. Patch at the module that looks up the name, not where it's defined.
Parametrize
@pytest.mark.parametrize("count,name", [(3, "a"), (10, "b")])
def test_seed_ingests(count, name): ...
What ships with it
2 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.
- 3d ago First seen · 121 lines · 30 tokens per session scan A 60c21ba6d020
pytest-testing is a skill published in the GitHub repository vikasudasi/skill-vault (0 stars, last pushed 18d ago), licensed Apache-2.0. It adds 30 tokens to every session and 995 once invoked, about $0.0002 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
pytest
Advanced Python unit testing framework for customer support tech enablement, covering FastAPI, SQLAlchemy, PostgreSQL, async operations, mocking, fixtures, parametrization, coverage, and comprehensive testing strategies for backend support systems.
pytest
Skill "pytest" from bobmatnyc/claude-mpm, covering pytest - professional python testing, basic pytest, with common plugins, for fastapi testing and for django testing.
pytest
Skill "pytest" from bobmatnyc/claude-mpm-skills, covering pytest - professional python testing, basic pytest, with common plugins, for fastapi testing and for django testing.
test-generator
Generate pytest test cases for Python functions and classes.
test-generator
Generate comprehensive unit, integration, and end-to-end tests. Use when adding test coverage, writing tests for new features, or improving existing test suites.
pytest-expert
Pytest fixtures, parametrize, mock/monkeypatch, async testing with pytest-asyncio, and coverage reporting.