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.
npx agentmods add rules/cpuguy96/stepcovnet/python-testsgit clone --depth 1 https://github.com/cpuguy96/StepCOVNetWhat 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 | $0.00000 | $0.01230 |
| Opus 5 | $0.00000 | $0.00615 |
| Sonnet 5 | $0.00000 | $0.00246 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
python-tests 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tests and coverage
When you add or modify code under src/, scripts/, or tests/:
- Update tests in
tests/(one test module per source module:stepcovnet/foo.py->tests/foo_test.py;scripts/bar.py->tests/bar_test.pywhen the script rule below applies). - Delta coverage ΓÇö aim for 100% of changed/new code via public API tests; high 90s only as last resort. Do not test private helpers solely for coverage.
- Lint with Ruff, pydoclint, and pyright on changed paths (
pyproject.tomlΓÇö import order, Google docstrings, pathlib, types):
venv\Scripts\python.exe -m ruff check .
venv\Scripts\pydoclint.exe src/stepcovnet/<package>/
venv\Scripts\pyright.exe src/stepcovnet/<package>/
Narrow paths to changed files/packages when appropriate. Docstring rules: python-style.mdc.
- Verify with Windows venv (see python-environment.mdc):
venv\Scripts\python.exe -m pytest tests/ -m "not slow" --cov=stepcovnet --cov=scripts
Use the relevant test file when scope is narrow. Import conventions beyond Ruff: python-style.mdc.
Scripts (scripts/)
Default: add tests/<script>_test.py in the same change when the script contains non-trivial parsing, discovery, path resolution, or CLI argument assembly (even if helpers are _private).
| Script shape | Tests required? | Where logic is covered |
|---|---|---|
Parsing / discovery / path logic (argparse, manifest walks, logdir specs, JSON config reads) |
Yes — tests/<script>_test.py |
Script tests + temp dirs; patch REPO when paths are repo-relative |
Thin CLI that only calls src/stepcovnet with no local logic |
No dedicated script test | Existing tests/ for the imported package |
Mixed (local helpers + src/ calls) |
Yes for the local helpers | Script tests for discovery/paths; package tests for core behavior |
Examples: audit_agent_brain.py → audit_agent_brain_test.py; project_status.py → project_status_test.py. Pattern: import the script module from tests/ via sys.path insert on scripts/ (see tests/conftest.py — set STEPCOVNET_NO_WSL=1 is already global).
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.
- yesterday First seen · 66 lines · 0 tokens per session scan A fc5d45f91f27
python-tests is a cursor rule published in the GitHub repository cpuguy96/StepCOVNet (21 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,230 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.
Other cursor rules, from other repositories
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.
workflows
This folder contains all GitHub Actions workflows for the Streamlit repository. Workflows automate CI/CD, testing, releases, and maintenance tasks.
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.
skills
This file provides guidance to AI coding agents (Claude Code, Cursor, Copilot, etc.) when working with skills in this repository.