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/state-and-pathsgit clone --depth 1 https://github.com/cpuguy96/StepCOVNetWrote 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/cpuguy96/stepcovnet/state-and-paths)<a href="https://agentmods.dev/rules/cpuguy96/stepcovnet/state-and-paths"><img src="https://agentmods.dev/badge/rules/cpuguy96/stepcovnet/state-and-paths.svg" alt="Measured on agentmods" 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 | $0.00797 | $0.00797 |
| Opus 5 | $0.00398 | $0.00398 |
| Sonnet 5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
state-and-paths 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 5d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State refresh and portable paths
When to refresh first
Before edits that touch linkages — routing (AGENTS.md), README, workflows, rules, skills, WSL shell scripts, docs cross-links, gitignore allowlists, or path conventions — refresh state:
git statusandgit log -1 --onelinegit ls-filesfor paths you will cite or link- Read target files; confirm they exist on disk (especially gitignored
docs/and.cursor/) - For WSL helpers: prefer
scripts/wsl_common.sh+ env vars over hardcoded clone or username paths
If a linked file is missing, fix the link or create the target — do not leave broken references in tracked files.
Machine-specific paths (tracked files only)
Use git grep, not workspace-wide search (gitignored local docs may contain stale paths):
git grep -E "C:\\\\Users|/mnt/c/Users/"
Expect no matches in tracked files.
Windows + WSL (portable)
| Workload | Pattern |
|---|---|
| Windows CPU | venv\Scripts\python.exe from repo root |
| WSL GPU Python | "${STEPCOVNET_WSL_PYTHON:-$HOME/stepcovnet-venv-wsl/bin/python}" (Linux $HOME, override with WSL_VENV) |
| WSL from Windows | venv\Scripts\python.exe scripts/... when script uses wsl_gpu dispatch |
| Data / models | data/v2, data/final_data, models_wsl/ (repo-relative) |
Never hardcode C:\Users\... or /mnt/c/Users/<name>/... clone paths. WSL $HOME/stepcovnet-venv-wsl is a project default venv name, not a machine-specific Windows path.
Disposable scratch (agents)
| Purpose | Path |
|---|---|
| One-off scripts, parse helpers, throwaway analysis | _tmp/<topic>/... (gitignored) |
| Command capture | logs/<topic>_<run>.log (gitignored) |
Do not create tmp_* or _tmp_* files at the repository root. Delete _tmp/ contents when done; never commit them.
On user steering about agent process (paths, hygiene, “remember this”), run steering-correction-promotion same turn — journal alone is incomplete.
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.
- 5d ago First seen · 64 lines · 797 tokens per session scan A 52e79e06f123
state-and-paths is a cursor rule published in the GitHub repository cpuguy96/StepCOVNet (22 stars, last pushed 11d ago), licensed Apache-2.0. It adds 797 tokens to every session, about $0.0040 per session on Opus 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 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.