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/denyszhak/pystack-skills/python-test-pyramidnpx skills add denyszhak/pystack-skills --skill python-test-pyramidgit clone --depth 1 https://github.com/denyszhak/pystack-skillsWhat 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.00194 | $0.03124 |
| Opus 5 | $0.00097 | $0.01562 |
| Sonnet 5 | $0.00039 | $0.00625 |
| Haiku 4.5 | $0.00019 | $0.00312 |
Grade A, and why
python-test-pyramid 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.
How it starts
The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test pyramid for FastAPI + SQLAlchemy
The testing strategy for an opinionated FastAPI + SQLAlchemy service. The core trade-off: real Postgres, protocol-level doubles for external systems. The DB is the part most likely to surprise you in production (constraints, transactions, types); external systems are where you want speed and determinism.
This skill encodes the canonical conftest, fixture organization, and test layout.
When to use this skill
- Setting up
tests/conftest.pyand fixtures for a new service - Adding a new test for a service, repo, route, or client
- Restructuring an existing test suite into unit / integration
- Diagnosing flaky tests, missing fixture wiring, or session lifetime issues
The layout
tests/
conftest.py # session-scoped: settings, db setup, app, db_pool. function-scoped: session, client.
fixtures/ # split fixture modules (pytest_plugins)
models.py
services.py
clients.py
repos.py
doubles/ # httpx.MockTransport handlers (one class per external client)
openai.py
stripe.py
unit/ # no DB, no HTTP — fast
schemas/ # cohesion methods (from_X, to_X)
common/ # exceptions, utilities, value objects
integration/ # real DB and/or external doubles
repos/ # exercises real DB
services/ # real DB + fake clients
api/ # full app via httpx ASGITransport
The rules
1. conftest.py at tests/ root, fixtures split by topic via pytest_plugins
# tests/conftest.py — shape; full version in examples/conftest.py
pytest_plugins = [
"tests.fixtures.models",
"tests.fixtures.services",
"tests.fixtures.clients",
"tests.fixtures.repos",
]
@pytest.fixture(scope="session")
def config() -> AppConfig:
return AppConfig()
Splitting fixtures into tests/fixtures/*.py keeps conftest.py short and lets you find a fixture by topic.
2. Real Postgres, set up once per test session
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.
- 2d ago First seen · 286 lines · 194 tokens per session scan A a86b7236bf21
python-test-pyramid is a skill published in the GitHub repository denyszhak/pystack-skills (4 stars, last pushed 3mo ago), licensed MIT. It adds 194 tokens to every session and 3,124 once invoked, about $0.0010 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…