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/batpool/upstox-totpWrote 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/batpool/upstox-totp/uv)<a href="https://agentmods.dev/rules/batpool/upstox-totp/uv"><img src="https://agentmods.dev/badge/rules/batpool/upstox-totp/uv/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/batpool/upstox-totp/uv"><img src="https://agentmods.dev/badge/rules/batpool/upstox-totp/uv.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.00293 | $0.00293 |
| Opus 5.5 | $0.00117 | $0.00117 |
| Sonnet 5.5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
uv 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 23d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- uv — 95% identical, 8 lines differ
- uv — 91% identical, 15 lines differ
- package-managment — 86% identical, 14 lines differ
What it actually says
Package Management with uv
These rules define strict guidelines for managing Python dependencies in this project using the uv dependency manager.
✅ Use uv exclusively
- All Python dependencies must be installed, synchronized, and locked using
uv. - Never use
pip,pip-tools, orpoetrydirectly for dependency management.
🔁 Managing Dependencies
Always use these commands:
# Add or upgrade dependencies
uv add <package>
# Remove dependencies
uv remove <package>
# Reinstall all dependencies from lock file
uv sync
🔁 Scripts
# Run script with proper dependencies
uv run script.py
You can edit inline-metadata manually:
# /// script
# requires-python = ">=3.12"
# dependencies = [
# "torch",
# "torchvision",
# "opencv-python",
# "numpy",
# "matplotlib",
# "Pillow",
# "timm",
# ]
# ///
print("some python code")
Or using uv cli:
# Add or upgrade script dependencies
uv add package-name --script script.py
# Remove script dependencies
uv remove package-name --script script.py
# Reinstall all script dependencies from lock file
uv sync --script script.py
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.
- 23d ago First seen · 68 lines · 293 tokens per session scan A f37c8c574c09
uv is a cursor rule published in the GitHub repository batpool/upstox-totp (15 stars, last pushed 8mo ago), licensed MIT. It adds 293 tokens to every session, about $0.0012 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-09-25.
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.