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/jenreh/appkit-bpmn-server/testing-python-pytestnpx skills add jenreh/appkit-bpmn-server --skill testing-python-pytestgit clone --depth 1 https://github.com/jenreh/appkit-bpmn-serverWhat 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.00124 | $0.01470 |
| Opus 5 | $0.00062 | $0.00735 |
| Sonnet 5 | $0.00025 | $0.00294 |
| Haiku 4.5 | $0.00012 | $0.00147 |
Grade A, and why
testing-python-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 yesterday.
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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python pytest Test Suite Generator
Generates comprehensive, production-quality pytest unit test suites that achieve >90% line and branch coverage per file.
Quick start
pip install pytest pytest-cov pytest-mock # Einmalig installieren
python scripts/analyze_module.py src/my_module.py # Modul analysieren
# → Schreibe tests/test_my_module.py (siehe Workflow unten)
python scripts/run_coverage.py src/my_module.py tests/test_my_module.py
Workflow
Kopiere diese Checkliste und hake ab:
Testing Progress:
- [ ] Step 1: Modul analysieren → analyze_module.py
- [ ] Step 2: Testdatei schreiben → AAA, Fixtures, Parametrize, Mocks
- [ ] Step 3: Coverage messen → run_coverage.py
- [ ] Step 4: Lücken schließen → Fehlende Zweige gezielt testen
- [ ] Step 5: ≥90 % bestätigt → Fertig ✓
Step 1 — Modul analysieren
python scripts/analyze_module.py <pfad/zum/modul.py>
Das Script gibt JSON aus mit: Klassen, Methoden, Funktionen, Typ-Hinweisen, Exception-Pfaden, Async-Code und konkreten Testing-Hints.
Step 2 — Testdatei schreiben
Dateiname: tests/test_<modulname>.py
Lese references/PYTEST_PATTERNS.md für
Fixtures, Parametrize, Mocking und Async-Tests.
Struktur jeder Testfunktion — AAA-Pflicht:
def test_<methode>_<szenario>(self, fixture):
# Arrange — Vorbedingungen und Eingaben
input_val = ...
# Act — Aktion unter Test
result = unit_under_test(input_val)
# Assert — Erwartetes Ergebnis prüfen
assert result == expected
Mindestabdeckung pro Einheit:
| Szenario | Pflicht |
|---|---|
| Happy path (Normalfall) | ✓ |
| Grenzwerte (0, -1, leer, None) | ✓ |
Exception-Pfade (pytest.raises) |
✓ je raise im Code |
Alle Bedingungszweige (if/else) |
✓ |
| Externe Abhängigkeiten gemockt | ✓ |
Step 3 & 4 — Coverage messen und Lücken schließen
python scripts/run_coverage.py <modul_pfad> <testdatei_pfad>
What ships with it
4 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.
- yesterday First seen · 191 lines · 124 tokens per session scan A df276cfafff3
testing-python-pytest is a skill published in the GitHub repository jenreh/appkit-bpmn-server (0 stars, last pushed 2mo ago), licensed MIT. It adds 124 tokens to every session and 1,470 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-31.
Other skills, from other repositories
python-binance
Help developers use the python-binance library for trading on Binance. Use when code imports binance, references Client/AsyncClient, or asks about Binance API trading, market data, websockets, or account management.
python-clean-code
Review Python code in the gsc-mcp codebase for clean code violations. Checks function size, single responsibility, type hints, naming, error handling patterns, and adherence to the project's module contracts. Use when refactoring a module or before code review.
gurume-cli
Use the gurume CLI to search Japanese restaurants on Tabelog. Trigger this whenever the user wants to find, recommend, or research restaurants/eateries in Japan — by area (Tokyo, Osaka, Kyoto, 三重, etc.), by cuisine (ramen, sushi, yakiniku, izakaya...), or with a vague request like "where should I eat in Shibuya" or…
swag
This skill should be used when the user says "add proxy config", "create reverse proxy", "SWAG config", "nginx proxy", "expose service", "proxy configuration", "subdomain config", "subfolder config", "configure SWAG", "list proxy configs", "view proxy config", "edit proxy config", "remove proxy config", "check proxy…
add-tool
Add a new MCP tool to this WhatsApp server. Use when asked to expose a new capability, wrap a new bridge endpoint, or add a tool to tools.py or scheduling.py. Covers annotations, the confirm guard, core-set placement, retrieval aliases, and the eval case.
onpage-audit
Complete on-page audit of a single URL in one pass, combining heading structure, internal linking, technical meta tags, content quality and schema, then cross-checked against real Search Console data before any recommendation is made. Use when asked for a full page audit, an all-in-one check, or what to fix on a page.…