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/jonlwowski012/copilot-agent-factory/pytest-setupnpx skills add jonlwowski012/copilot-agent-factory --skill pytest-setupgit clone --depth 1 https://github.com/jonlwowski012/copilot-agent-factoryWrote 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/jonlwowski012/copilot-agent-factory/pytest-setup)<a href="https://agentmods.dev/skills/jonlwowski012/copilot-agent-factory/pytest-setup"><img src="https://agentmods.dev/badge/skills/jonlwowski012/copilot-agent-factory/pytest-setup.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.00016 | $0.02051 |
| Opus 5 | $0.00008 | $0.01026 |
| Sonnet 5 | $0.00003 | $0.00410 |
| Haiku 4.5 | $0.00002 | $0.00205 |
Grade A, and why
pytest-setup 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 6d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Test Framework Setup (pytest)
When to Use This Skill
This skill activates when you need to:
- Set up pytest from scratch in a Python project
- Add coverage reporting to existing tests
- Configure watch mode for test-driven development
- Fix broken pytest configurations
Prerequisites
Check if testing is already configured:
- Look for {{test_dirs}} (e.g.,
tests/,test/, or__tests__/) - Check for
pytestinrequirements.txt,pyproject.toml, orPipfile - Verify {{test_command}} exists in project configuration
If already configured: This skill provides configuration improvements and troubleshooting.
Step-by-Step Workflow
Step 1: Install pytest and Extensions
If using pip (requirements.txt):
pip install pytest pytest-cov pytest-watch
Add to requirements.txt or requirements-dev.txt:
pytest>=7.4.0
pytest-cov>=4.1.0
pytest-watch>=4.2.0
If using Poetry:
poetry add --group dev pytest pytest-cov pytest-watch
If using Pipenv:
pipenv install --dev pytest pytest-cov pytest-watch
If using conda:
conda install pytest pytest-cov
pip install pytest-watch
Step 2: Create Test Directory Structure
# Create main test directory
mkdir -p tests
# Create __init__.py to make it a package
touch tests/__init__.py
# Create conftest.py for shared fixtures
touch tests/conftest.py
# Create your first test file
touch tests/test_example.py
Add a sample test to tests/test_example.py:
def test_basic_example():
"""Basic example test to verify pytest is working."""
assert 1 + 1 == 2
def test_string_operations():
"""Test string operations."""
assert "hello".upper() == "HELLO"
Step 3: Add pytest Configuration
Option A: pytest.ini (Recommended)
Create pytest.ini in project root:
[pytest]
testpaths = tests
python_files = test_*.py *_test.py
python_classes = Test*
python_functions = test_*
addopts =
-v
--strict-markers
--cov=src
--cov-report=html
--cov-report=term-missing
--cov-report=xml
markers =
slow: marks tests as slow (deselect with '-m "not slow"')
integration: marks tests as integration tests
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.
- 6d ago First seen · 350 lines · 16 tokens per session scan A 0a0b760f9c1b
pytest-setup is a skill published in the GitHub repository jonlwowski012/copilot-agent-factory (16 stars, last pushed 5d ago), licensed MIT. It adds 16 tokens to every session and 2,051 once invoked, about $0.0001 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
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
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…
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
add-go-test
Write or extend Go unit tests in this repo. Use when the user asks to add or update Go tests.