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/mitas/cursor-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/rules/mitas/cursor-rules/uv-tool-usage)<a href="https://agentmods.dev/rules/mitas/cursor-rules/uv-tool-usage"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/uv-tool-usage/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/mitas/cursor-rules/uv-tool-usage"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/uv-tool-usage.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.00000 | $0.01297 |
| Opus 5.5 | $0.00000 | $0.00519 |
| Sonnet 5.5 | $0.00000 | $0.00259 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
uv-tool-usage 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UV Tool Usage
Basic Commands
- Create virtual environments with:
uv venvinstead ofpython -m venv - Install packages with:
uv pip install packageinstead ofpip install package - Run Python scripts with:
uv run python script.pyinstead ofpython script.py - Initialize a new project:
uv init myproject - Generate lockfile:
uv lock - Install dependencies from lockfile:
uv sync - Run commands in project environment:
uv run command
Project Management
- Use uv for all project management:
uv init myproject - Create standard project structure with:
- pyproject.toml - Project configuration
- src/ - Source code directory
- .venv/ - Virtual environment (created when needed)
- uv.lock - Lockfile for dependencies
- Add dependencies with:
uv add package - Add dev dependencies with:
uv add --dev package - Remove dependencies with:
uv remove package - Update dependencies with:
uv update - Show installed packages with:
uv list
Package Management
- Build packages with:
uv build - Publish to PyPI with:
uv publish - Manage dependencies with uv instead of poetry or pip-tools:
uv pip compile pyproject.toml -o requirements.txtto generate requirementsuv syncto install dependencies from lockfile (preferred method)uv pip sync requirements.txtas alternative for requirements.txt files
Python Version Management
- Install specific Python versions:
uv python install 3.11 - List installed Python versions:
uv python list - Pin project to a Python version:
uv python pin 3.11 - Create virtual environment with specific Python:
uv venv --python 3.12.0 - Use specific Python version:
uv run --python 3.11 script.py
Tool Management
- Run tools in ephemeral environments with:
uvx tool-name(e.g.,uvx pytest) - Install tools globally with:
uv tool install ruff - List installed tools with:
uv tool list - Uninstall tools with:
uv tool uninstall ruff - Run Python-based tools without installing:
uvx tool-name
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 · 139 lines · 1,297 tokens per session scan A 1dff065243ff
uv-tool-usage is a cursor rule published in the GitHub repository mitas/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,297 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-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.