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/maoxx241/vllm-ascend-workspace/commit-conventionsgit clone --depth 1 https://github.com/maoxx241/vllm-ascend-workspaceWhat 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.00016 | $0.00134 |
| Opus 5 | $0.00008 | $0.00067 |
| Sonnet 5 | $0.00003 | $0.00027 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
commit-conventions 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 3d 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.
What it actually says
Commit Conventions
Scaffold repository (this repo)
Standard conventional commits:
<type>: <summary>
Types: feat, fix, refactor, docs, chore, test
vllm-ascend submodule
Commits inside vllm-ascend/ must follow the submodule's own conventions — always read vllm-ascend/AGENTS.md for the current commit format, sign-off requirements, and PR title rules.
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.
- 3d ago First seen · 21 lines · 16 tokens per session scan A cac84062ed10
commit-conventions is a cursor rule published in the GitHub repository maoxx241/vllm-ascend-workspace (32 stars, last pushed 5d ago), licensed MIT. It adds 16 tokens to every session and 134 once invoked, about $0.0001 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-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
git-conventional-commits
Conventional commit messages and logical multi-commit workflow when working with Git.
dos-verify-done-claims-cursorrules-prompt-file
Gate AI done/shipped/fixed claims on ground truth from the DOS kernel (dos verify, dos commit-audit) — git ancestry and the commit's own diff, never the agent's own narration.
pause
Checkpoint the session into git so it survives a close and resumes from any device. Use on "pause", "checkpoint", "cache this session", "save my place", or "I'm stepping away" — writes a handoff, commits work in flight, and pushes.
no-cursor-commit-attribution
Never add Cursor co-author or attribution trailers to git commits or PRs.
git-commits
description: "Reference and apply the git commits skill for Conventional Commit formatting and pre-push checks." alwaysApply: true.