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/pingcap/pytidb/commit-messagegit clone --depth 1 https://github.com/pingcap/pytidbWhat 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.00003 | $0.00075 |
| Opus 5 | $0.00002 | $0.00037 |
| Sonnet 5 | $0.00001 | $0.00015 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
commit-message 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 yesterday.
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.
What it actually says
Example commit messages:
- feat: support prefilter for table.search() API
- refactor: unify create mode and exist_ok to be if_exists="skip"
- build: bump pytidb version to 0.0.10.dev1
- docs: add image search example
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.
- yesterday First seen · 13 lines · 3 tokens per session scan A 31bb3dc8d826
commit-message is a cursor rule published in the GitHub repository pingcap/pytidb (33 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 3 tokens to every session and 75 once invoked, about $0.0000 per session on Opus 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
git-conventions
See CONTRIBUTING.md → "PR & commit conventions" for PR title format, commit messages, and branch naming.
trigger.advanced-tasks
Comprehensive rules to help you write advanced Trigger.dev tasks.
project-structure
Project structure, monorepo management, and architectural patterns for the Agentset platform.
trigger.basic
Only the most important rules for writing basic Trigger.dev tasks.
debug-capture-pipeline
Debug llm-wiki-memory capture/recall — flush breadcrumbs, daily-vs-compile lag, failed-distill stash recovery, embedding cache, hook wiring. Use when memory didn't capture, doesn't recall, or a hook/cron looks broken.
docs-style
README and docs style for llm-wiki-memory — install-first structure, plain-English jargon, vertical Mermaid with quoted labels, badge rules. Canonical file is .agents/rules/docs-style.md.