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 dvf/opinionated-django --skill dj-pytestgit clone --depth 1 https://github.com/dvf/opinionated-djangoWrote 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/dvf/opinionated-django/dj-pytest)<a href="https://agentmods.dev/skills/dvf/opinionated-django/dj-pytest"><img src="https://agentmods.dev/badge/skills/dvf/opinionated-django/dj-pytest/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/dvf/opinionated-django/dj-pytest"><img src="https://agentmods.dev/badge/skills/dvf/opinionated-django/dj-pytest.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.00114 | $0.03864 |
| Opus 5 | $0.00057 | $0.01932 |
| Sonnet 5 | $0.00023 | $0.00773 |
| Haiku 4.5 | $0.00011 | $0.00386 |
Grade A, and why
dj-pytest 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 9d 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pytest for op-django
Testing in this project is layered the same way the code is. Each layer has its own rules, its own fixtures, and its own performance characteristics. The goal is to keep the fast tests fast — service tests should never touch a database — and to isolate the slow tests at the edges.
The Three Layers
| File | What it covers | DB? | Speed |
|---|---|---|---|
test_repo.py |
ORM ↔ DTO conversion, prefetches, transactions, ID prefixes | ✅ real | slow |
test_service.py |
Business logic, validation, orchestration | ❌ mocked | fast |
test_api.py |
HTTP integration — request → view → service → repo | ✅ real | slow |
Service tests are the most valuable layer and should outnumber the others. If a service test needs @pytest.mark.django_db, something has leaked — find the ORM call and push it into a repository.
Dependencies
uv add --dev pytest pytest-django pytest-xdist freezegun pytest-mock
- pytest-django — the
django_dbmarker,clientfixture, settings integration,django_capture_on_commit_callbacks. - pytest-xdist —
-n autoparallel runs. Keep it out ofaddoptsso debugger runs stay serial. - pytest-celery is deliberately absent — tasks are never executed through Celery machinery in tests (see Celery in Tests).
- freezegun — freezes
datetime.now(),time.time(), and friends. Required for any logic that touches timestamps, TTLs, scheduled work, or ULIDs whose sort order matters to the test. - pytest-mock — the
mockerfixture (a thin wrapper aroundunittest.mockwith autouse cleanup).
Configuration
Add to pyproject.toml:
[tool.pytest.ini_options]
DJANGO_SETTINGS_MODULE = "project.settings"
python_files = ["test_*.py"]
pythonpath = ["src"]
addopts = [
"-ra",
"--strict-markers",
"--strict-config",
]
markers = [
"slow: deselect with '-m \"not slow\"'",
]
Notes:
pythonpath = ["src"]is what letsfrom project.services import getresolve without an editable install.--strict-markerscatches typos in@pytest.mark.xxx.--strict-configdoes the same for the config file.- Keep the
markerslist small and meaningful — one or two genuine custom markers maximum.
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.
- 9d ago First seen · 379 lines · 114 tokens per session scan A a8df7c5dc1e9
dj-pytest is a skill published in the GitHub repository dvf/opinionated-django (110 stars, last pushed 26d ago), licensed MIT. It adds 114 tokens to every session and 3,864 once invoked, about $0.0006 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
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.