pytest_unit_test_rules

pytest_unit_test_rules is a cursor rule for Cursor from ModelEngine-Group/nexent. It costs 0 tokens per session (99 once invoked), scanned A, original, MIT.

A set of rules for writing unit tests with pytest, a Python testing tool. It covers test names, imports, mocking, file size, coverage, and asynchronous code.

In plain words
What is it for?
Use it when adding or changing Python unit tests, fixtures, mocks, async tests, or test file organization.
Why use it?
It gives tests a consistent structure and helps ensure success cases, errors, and boundary conditions are checked without calling outside services directly.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when adding or changing Python unit tests, fixtures, mocks, async tests, or test file organization.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/modelengine-group/nexent/pytest_unit_test_rules
About the project

Nexent is a zero-code platform for creating AI agents from natural-language instructions, combining tools, skills, memory, orchestration, constraints, feedback loops, and control planes. It is intended for people who need to build and deploy agents without writing orchestration code. The catalogue entries are rules and skills for working with Nexent.

ModelEngine-Group/nexent · 5,955 stars · on GitHub · modelengine-group.github.io

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.

Clone the repo
git clone --depth 1 https://github.com/ModelEngine-Group/nexent

Made for: Cursor.

Wrote 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.

agentmods badge for pytest_unit_test_rules

README.md
[![agentmods](https://agentmods.dev/badge/rules/modelengine-group/nexent/pytest_unit_test_rules/github.svg)](https://agentmods.dev/rules/modelengine-group/nexent/pytest_unit_test_rules)
Your own site
<a href="https://agentmods.dev/rules/modelengine-group/nexent/pytest_unit_test_rules"><img src="https://agentmods.dev/badge/rules/modelengine-group/nexent/pytest_unit_test_rules/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.

agentmods 80×15 button for pytest_unit_test_rules

Your own site · 80×15
<a href="https://agentmods.dev/rules/modelengine-group/nexent/pytest_unit_test_rules"><img src="https://agentmods.dev/badge/rules/modelengine-group/nexent/pytest_unit_test_rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 99 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00099
Opus 5.5 $0.00000 $0.00040
Sonnet 5.5 $0.00000 $0.00020
Haiku 4.5 $0.00000 $0.00010

Measured 1mo ago against content hash 2c4a4a290bf9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pytest_unit_test_rules 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 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.

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.

.cursor/rules/pytest_unit_test_rules.mdc · 11 lines

What it actually says

Shared project rules

Read .agents/skills/nexent-python-tests/SKILL.md before working in this rule scope.

Paths are relative to the repository root. If linked context is unavailable, read the file directly. Load only applicable references. Maintain the linked Markdown source instead of duplicating rules here.

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. 1mo ago Changed · -41 lines 2c4a4a290bf9
  2. 1mo ago First seen · 52 lines · 0 tokens per session scan A f51c66663f80

Subscribe to this mod's changes

pytest_unit_test_rules is a cursor rule published in the GitHub repository ModelEngine-Group/nexent (5,955 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 99 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.