Borrowing it
Nothing to install: this file belongs to iloveitaly/llm-ide-rules. 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/iloveitaly/llm-ide-rules/master/.github/instructions/pytest-tests.instructions.mdgit clone --depth 1 https://github.com/iloveitaly/llm-ide-rulesWrote 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/instructions/iloveitaly/llm-ide-rules/pytest-tests)<a href="https://agentmods.dev/instructions/iloveitaly/llm-ide-rules/pytest-tests"><img src="https://agentmods.dev/badge/instructions/iloveitaly/llm-ide-rules/pytest-tests/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/instructions/iloveitaly/llm-ide-rules/pytest-tests"><img src="https://agentmods.dev/badge/instructions/iloveitaly/llm-ide-rules/pytest-tests.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.00675 | $0.00675 |
| Opus 5.5 | $0.00270 | $0.00270 |
| Sonnet 5.5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
llm-ide-rules pytest-tests.instructions.md 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 19d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pytest Tests
- Look first to
app.factories.*instead ofapp.models.*to generate any required database state- For example, to create and persist a
DistributionrecordDistributionFactory.save() - If a factory doesn't exist for the model you are working with, create one.
- You can customize one or more params in a factory using
DistributionFactory.save(host="custom_host.com)
- For example, to create and persist a
- Use
fakerfactory to generate emails, etc. - Do not mock or patch unless I instruct you to. Test as much of the application stack as possible in each test.
- If you get lazy attribute errors, or need a database session to share across logic, use the
db_sessionfixture to fix the issue.- Note that when writing route tests a
db_sessionis not needed for the logic inside of the route.
- Note that when writing route tests a
- When testing Stripe, use the sandbox API. Never mock out Stripe interactions unless explicitly told to.
- Omit obvious docstrs and comments. Add comments for non-obvious but easy-to-miss lines that are key to what the test is checking.
- Do not add multiple tests for a one-line change.
- If test state setup requires more than three distinct factories, you should probably create a new factory to represent this particular state.
- Add pre-condition assertions when setup is load-bearing.
- If a
monkeypatchis truly needed, a one-line comment on why. Prefer full-stack testing over mocking.
Example Test
Below is an example test, you'll notice the following:
- Docstr is omitted since the purpose of the test is obvious
- Comment about the
countyis added since it's the main point of the test - Newline between test setup, functionality under test, and assertions against result
api_app_url_path_forhelper is used instead of hardcoded routes
from app.generated.fastapi_typed_routes import api_app_url_path_for
import json
def test_calculate_quote_unknown_county(client):
payload = {
"subscriber": {"age": 35, "gender": "M"},
# fake county to ensure error is thrown
"county": "NotACounty",
}
response = client.post(
api_app_url_path_for("composite_quote"),
json=payload,
)
assert_status(response, status.HTTP_422_UNPROCESSABLE_CONTENT)
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.
- 19d ago Changed · +4 lines · +77 tokens per session 1c0edcebad03
- 28d ago Changed · -1 lines e799a6036f2e
- 1mo ago Changed · +2 lines · +37 tokens per session dff68dc398b4
- 1mo ago First seen · 54 lines · 561 tokens per session scan A 15544eeb580b
llm-ide-rules pytest-tests.instructions.md is an instructions file published in the GitHub repository iloveitaly/llm-ide-rules (13 stars, last pushed yesterday), licensed MIT. It adds 675 tokens to every session, about $0.0027 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.