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/TACC/HPCPerfStatsWrote 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/tacc/hpcperfstats/python-image-interpreter-contract)<a href="https://agentmods.dev/rules/tacc/hpcperfstats/python-image-interpreter-contract"><img src="https://agentmods.dev/badge/rules/tacc/hpcperfstats/python-image-interpreter-contract/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/tacc/hpcperfstats/python-image-interpreter-contract"><img src="https://agentmods.dev/badge/rules/tacc/hpcperfstats/python-image-interpreter-contract.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.03409 |
| Opus 5.5 | $0.00000 | $0.01364 |
| Sonnet 5.5 | $0.00000 | $0.00682 |
| Haiku 4.5 | $0.00000 | $0.00341 |
Grade C, and why
python-image-interpreter-contract scanned grade C with 1 finding 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 today.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| zlib-ng (direct link) | Pin **zlib-ng** under **`/opt/zlib-ng`** with **`ZLIB_COMPAT=ON`** (ThinLTO bake flags). Link **both** CPythons and source-built numpy/numexpr/pandas with **`-I/opt/zlib-ng/include`**, **`-L/opt The source is not reproduced here
Licensed LGPL-2.1
The repository is licensed LGPL-2.1, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- today Changed 01a38f05f699
- 13d ago Changed c2052e9bfcee
- 14d ago Changed 2301f99871d2
- 15d ago Changed 0784be82aa0c
- 16d ago Changed · +1 lines 8942645fd582
- 20d ago Changed 6cedb794ef90
- 1mo ago Changed · +1 lines b06672d2c8d5
- 1mo ago Changed 84567452b8be
- 1mo ago Changed · +3 lines scan A → C fbf81f0d8405
- 1mo ago First seen · 47 lines · 0 tokens per session scan A ac3362e00cff
python-image-interpreter-contract is a cursor rule published in the GitHub repository TACC/HPCPerfStats (59 stars, last pushed today), licensed LGPL-2.1. It costs nothing until one of its globs matches a file; then it loads 3,409 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other cursor rules, from other repositories
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
python-containerization-cursorrules-prompt-file
description: "Cursor rules for Python development with containerization integration." globs: / alwaysApply: false.
chainguard-libraries-python
Suggest Chainguard Libraries when adding or updating Python dependencies.
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.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
python
At the start of your every response, say "APPLIED PYTHON RULE".