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/tacc/hpcperfstats/plan-template-enforcementgit clone --depth 1 https://github.com/TACC/HPCPerfStatsWhat 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.00000 | $0.01622 |
| Opus 5 | $0.00000 | $0.00811 |
| Sonnet 5 | $0.00000 | $0.00324 |
| Haiku 4.5 | $0.00000 | $0.00162 |
Grade A, and why
plan-template-enforcement 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 2d 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.
- 2d ago First seen · 83 lines · 0 tokens per session scan A df4b8d225865
plan-template-enforcement is a cursor rule published in the GitHub repository TACC/HPCPerfStats (58 stars, last pushed 2d ago), licensed LGPL-2.1. It costs nothing until one of its globs matches a file; then it loads 1,622 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-30.
Other cursor rules, from other repositories
coding-agents-convention
Canonical coding-agent telemetry schema, inbound mappings, and data contracts. Applies to semantic conventions, emission, processing, and readers—not hook implementation mechanics.
coding-agents-hook
Authoring and testing coding-agent hook adapters, including payload probing, session state, capture modes, and plugin manifests. Consult the telemetry convention when changing canonical attributes.
controller-design
Design principles and invariants for the OpenLIT controller (Go agent that discovers and instruments LLM workloads) and the Agents-page server layer that consumes its data.
security-testing
Authorization, input validation, CE boundary, secrets, and test guidance for OpenLIT server code.
documentation
Standards for OpenLIT documentation, MDX structure, navigation, examples, and terminology.
js-sdk-genai-instrumentation
Guide for aligning JS SDK GenAI provider instrumentations with OTel semantic conventions and the Python SDK reference implementation.