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.
git clone --depth 1 https://github.com/joaovicdev/nemesisWrote 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/rules/joaovicdev/nemesis/python)<a href="https://agentmods.dev/rules/joaovicdev/nemesis/python"><img src="https://agentmods.dev/badge/rules/joaovicdev/nemesis/python/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/rules/joaovicdev/nemesis/python"><img src="https://agentmods.dev/badge/rules/joaovicdev/nemesis/python.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.00569 | $0.00569 |
| Opus 5.5 | $0.00228 | $0.00228 |
| Sonnet 5.5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
python 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Standards
Type Annotations
- All function signatures MUST have type annotations — parameters and return types.
- Use
from __future__ import annotationsat the top of every module to enable postponed evaluation of annotations. - Prefer
X | Yunion syntax overOptional[X]orUnion[X, Y]. - Use
TypeAliasfor complex types used in multiple places.
# Good
async def analyze(output: str, context: ProjectContext) -> list[Finding]: ...
# Bad
def analyze(output, context): # no types
Async / Await
- All I/O operations (subprocess, database, LLM calls, HTTP) MUST be
async. - Use
asyncio.create_task()for fire-and-forget background work. - Use
asyncio.gather()for parallel independent operations (e.g. running multiple tools). - Never use
time.sleep()— useawait asyncio.sleep(). - Never call blocking I/O in async functions — use
asyncio.to_thread()if needed.
Data Models
- Use
pydantic.BaseModelfor all data models exchanged between layers (Finding,Project,Session,AgentEvent, etc.). - Use
dataclasses.dataclassonly for simple internal data containers that do not cross layer boundaries. - All models that are persisted to SQLite must have an
id: strfield (UUID).
Logging
- NEVER use
print()in production code. Uselogging.getLogger(__name__). - In TUI code, emit Textual messages/events instead of logging directly.
- Log levels:
DEBUGfor raw tool output,INFOfor agent state changes,WARNINGfor unexpected conditions,ERRORfor failures.
Code Style
- Maximum line length: 100 characters.
- Use
rufffor formatting and linting — runuv run ruff checkanduv run ruff format. - Prefer early returns over deeply nested conditionals.
- Prefer named constants over magic strings — define them at module level in UPPER_CASE.
- All exceptions should be caught at boundaries (agents, tool runners) and converted to typed result objects — never let raw exceptions propagate to the TUI.
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 · 67 lines · 569 tokens per session scan A 7f0d4b82282a
python is a cursor rule published in the GitHub repository joaovicdev/nemesis (4 stars, last pushed 5mo ago), licensed MIT. It adds 569 tokens to every session, about $0.0023 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-31.
Other cursor rules, from other repositories
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
python-llm-ml-workflow-cursorrules-prompt-file
Cursor rules for Python LLM & ML development with workflow integration.
python
Python best practices and patterns for modern software development with Flask and SQLite.
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
rich
Definitive guidelines for building robust, maintainable, and visually appealing Python CLI applications using the rich library.