Borrowing it
Nothing to install: this file belongs to timothywarner/copilot-dev. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/timothywarner/copilot-dev/main/.github/prompts/Pytest Coverage Prompt.prompt.mdgit clone --depth 1 https://github.com/timothywarner/copilot-devWrote 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/commands/timothywarner/copilot-dev/pytest-coverage-prompt)<a href="https://agentmods.dev/commands/timothywarner/copilot-dev/pytest-coverage-prompt"><img src="https://agentmods.dev/badge/commands/timothywarner/copilot-dev/pytest-coverage-prompt/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/commands/timothywarner/copilot-dev/pytest-coverage-prompt"><img src="https://agentmods.dev/badge/commands/timothywarner/copilot-dev/pytest-coverage-prompt.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.01261 |
| Opus 5.5 | $0.00006 | $0.00504 |
| Sonnet 5.5 | $0.00003 | $0.00252 |
| Haiku 4.5 | $0.00001 | $0.00126 |
Grade A, and why
Pytest Coverage Prompt scanned grade A 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
with patch("your_module.requests.get") as mock_get: How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your goal is to analyze the current pytest test coverage for this project and add tests to bring all modules to at least 80% line coverage — the minimum standard for this codebase.
Step 1: Run the coverage report
Run the annotated coverage report so we can see exactly which lines are uncovered:
# For the whole project
pytest --cov --cov-report=annotate:cov_annotate --cov-report=term-missing -v
# For a specific module (replace MODULE_NAME if provided)
pytest --cov=${input:module:tip_service} --cov-report=annotate:cov_annotate --cov-report=term-missing -v
# For a specific test file only
pytest ${input:testfile:tests/} --cov --cov-report=term-missing -v
Step 2: Interpret the results
In the cov_annotate/ directory, each source file has an annotated copy:
- Lines starting with
>are executed (covered) - Lines starting with
!are NOT covered — these need tests - Lines starting with
-are excluded (comments, blanks)
In the terminal report, focus on the Miss column — those are the uncovered line numbers.
Step 3: Generate missing tests
For each uncovered section, generate tests following these patterns:
Basic test structure (pytest style)
import pytest
from your_module import the_function_under_test
class TestFunctionName:
"""Tests for the_function_under_test."""
def test_happy_path(self):
"""Verify normal operation with valid inputs."""
result = the_function_under_test("valid_input")
assert result == "expected_output"
def test_edge_case_empty_input(self):
"""Verify behavior with empty/None input."""
result = the_function_under_test("")
assert result == "" # or pytest.raises(ValueError)
def test_error_condition(self):
"""Verify correct exception is raised for invalid input."""
with pytest.raises(ValueError, match="meaningful message"):
the_function_under_test(None)
Fixtures — prefer fixtures over repetition
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.
- 1mo ago First seen · 179 lines · 14 tokens per session scan A c8775e11f4c6
Pytest Coverage Prompt is a command published in the GitHub repository timothywarner/copilot-dev (46 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 1,261 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-20.
Other commands, from other repositories
session
Complete guide to managing pair programming sessions.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
lg:node
Create, modify, and manage nodes in LangGraph graphs including LLM nodes, tool nodes, human-in-the-loop, subgraphs, and conditional nodes.
test-audit
Writes a versioned TESTAUDIT.md; with --fix, quarantines the rot in gated, revertible commits. TRIGGER WHEN: auditing a test suite, measuring test health, finding dead or flaky or redundant tests, or diagnosing failure causes and proposing temporary quarantine. DO NOT TRIGGER WHEN: one module's tests are consolidated…
story-and-test
For the component(s) in scope.