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/job-plot-artifacts-caching)<a href="https://agentmods.dev/rules/tacc/hpcperfstats/job-plot-artifacts-caching"><img src="https://agentmods.dev/badge/rules/tacc/hpcperfstats/job-plot-artifacts-caching/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/job-plot-artifacts-caching"><img src="https://agentmods.dev/badge/rules/tacc/hpcperfstats/job-plot-artifacts-caching.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.00021 | $0.02173 |
| Opus 5.5 | $0.00008 | $0.00869 |
| Sonnet 5.5 | $0.00004 | $0.00435 |
| Haiku 4.5 | $0.00002 | $0.00217 |
Grade A, and why
job-plot-artifacts-caching 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.
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.
- 1mo ago Changed d7b8719508d6
- 1mo ago First seen · 71 lines · 21 tokens per session scan A 3e9587979f81
job-plot-artifacts-caching is a cursor rule published in the GitHub repository TACC/HPCPerfStats (59 stars, last pushed today), licensed LGPL-2.1. It adds 21 tokens to every session and 2,173 once invoked, about $0.0001 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-08-30.
Other cursor rules, from other repositories
redis
This guide provides definitive, actionable best practices for using Redis effectively, focusing on data modeling, performance, security, and cluster-aware client usage to build robust and scalable applications.
cache
A set of guidance for using a cache, a temporary data store that keeps frequently needed information available for faster access. It describes cache operations and a shared data center for access to stored data.
spring-boot-redis
Spring Boot Redis contract for connection settings, RedisTemplate datastore access, Spring Cache with Redis, and Redis Pub/Sub.
redis
This rule provides best practices for working with Redis, covering code organization, performance, security, testing, and common pitfalls to ensure efficient and reliable usage. It applies to any language file interacting with Redis.
canonical__eedis
Redis: data structures, caching patterns, pub/sub.
nosql-specialist-intelligent
NoSQL database specialist for document stores, key-value databases, and distributed data systems. Apply this rule when working with MongoDB for flexible document storage and aggregation pipelines, implementing Redis for caching and real-time features with data structures, designing Cassandra schemas for time-series…