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 darellchua2/opencode-config-template --skill python-pytest-creator-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/python-pytest-creator-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/python-pytest-creator-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/python-pytest-creator-skill.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.1 | $0.00021 | $0.02742 |
| Opus 5 | $0.00010 | $0.01371 |
| Sonnet 5 | $0.00004 | $0.00548 |
| Haiku 4.5 | $0.00002 | $0.00274 |
Grade C, and why
python-pytest-creator-skill scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
When protocol is enabled, this skill defaults to `Iterations: 10` (sufficient for typical single-pass workflows). Override with `Iterations: N` for specific tasks. Safety blocks: `.env`, `node_modules/`, `rm -rf`, `git p How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I implement a complete Python pytest test generation workflow by extending the test-generator-framework:
- Analyze Python Codebase: Scan Python application to identify functions, classes, and modules
- Detect Python Testing Setup: Identify pytest version and Poetry availability
- Generate Python-Specific Scenarios: Create comprehensive test scenarios covering:
- Happy paths, edge cases, and error handling
- Python-specific patterns (decorators, context managers, async functions)
- Delegate to Framework: Use
test-generator-frameworkfor core test generation workflow - Ensure Executability: Verify tests run with
poetry run pytestorpytest
When to use me
Use this workflow when:
- You need to create comprehensive pytest test files for a Python application
- You want to ensure all edge cases and error conditions are covered
- You need tests that integrate with Poetry environments
- You prefer a systematic approach to test generation with user confirmation
- You want to ensure tests run correctly with your project's pytest version
Framework: This skill extends test-generator-framework for core test generation workflow, adding Python-specific functionality.
Prerequisites
- Python project with Poetry (
pyproject.toml) or pip (requirements.txt) - Pytest installed and configured in project
- Python source code to test
- Appropriate file permissions to create test files
Note: Poetry is optional. If Poetry is installed and pyproject.toml exists, tests will use poetry run pytest. Otherwise, tests will use pytest directly.
Steps
Step 1: Analyze Python Codebase
- Use glob patterns to find Python files:
**/*.py - Exclude test files:
**/test_*.py,**/*_test.py,**/tests/**/*.py - Read each Python file to identify:
- Functions:
def function_name(parameters): - Classes:
class ClassName: - Methods:
def method_name(self, parameters): - Async functions:
async def async_function(): - Decorators:
@decorator_name - Context managers:
with context_manager():
- Functions:
- Identify import statements to understand dependencies
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.
- 4d ago First seen · 350 lines · 21 tokens per session scan C 213ce4f1d9c5
python-pytest-creator-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 21 tokens to every session and 2,742 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
test-corpus
The testdocuments submodule is a bucket-fetched fixture corpus that is not committed. This skill covers readtestfixture, missing fixtures, valid A/B controls, and submodule push order. Load before running Rust tests on a fresh clone, setting up an A/B control, adding a fixture-backed test, or diagnosing…
python-providers
Create, modify, test, or package Python provider adapters under python/providers, including framework-specific dependencies, public imports, type inference, and provider metadata. Use for Python provider work only; use python-sdk for core SDK changes.
xberg-typescript-toolchain
Work on Xberg TypeScript or JavaScript packages with the repository's actual poly, pnpm, npm, Vitest, napi-rs, wasm-pack, and integration-package boundaries. Load for TS/JS tooling or package changes, not Rust-only binding generation.
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…