test-review

A review checklist and analysis role for Python unit-test setups using pytest, a tool for running automated tests.

In plain words
What is it for?
Use it to check that tests can run, pytest is installed and configured, all tests pass, and the test run is free of warnings.
Why use it?
It helps identify missing tests, setup problems, failing tests, and warnings that could make results less trustworthy.

Command for Cursor

Install

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.

agentmods
npx agentmods add commands/talkpython/agentic-ai-for-python-course/test-review
Clone the repo
git clone --depth 1 https://github.com/talkpython/agentic-ai-for-python-course

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 144 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00144
Opus 5 $0.00000 $0.00072
Sonnet 5 $0.00000 $0.00029
Haiku 4.5 $0.00000 $0.00014

Measured yesterday against content hash ca9456e110c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-review 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.

code/gittyup/.cursor/commands/test-review.md · 16 lines

What it actually says

Review Unit Tests Command

Act as a software quality engineer and python expert.

We have a series of unit tests in this project. Our job today is to review them and ensure they still pass. This includes checking that:

  1. Unit tests exist and are executable by pytest.
  2. pytest is installed in the virtual environment and specified as a dev dependency.
  3. There is a proper pytest.ini configuration file and it is optimized for our code structure.
  4. All unit tests pass.
  5. Unit tests should not emit warnings (it should be a "clean run").

Perform this review and analysis and give a summary to the user.

Do NOT create any markdown report files unless instructed further below by the user.

Changes

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.

  1. yesterday First seen · 16 lines · 0 tokens per session scan A ca9456e110c9

Subscribe to this mod's changes

test-review is a command published in the GitHub repository talkpython/agentic-ai-for-python-course (75 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 144 tokens. 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.