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/RandyChen1985/nanzi-ai-agent-platformWrote 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/randychen1985/nanzi-ai-agent-platform/pull-request-template)<a href="https://agentmods.dev/rules/randychen1985/nanzi-ai-agent-platform/pull-request-template"><img src="https://agentmods.dev/badge/rules/randychen1985/nanzi-ai-agent-platform/pull-request-template/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/randychen1985/nanzi-ai-agent-platform/pull-request-template"><img src="https://agentmods.dev/badge/rules/randychen1985/nanzi-ai-agent-platform/pull-request-template.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.00320 | $0.00320 |
| Opus 5.5 | $0.00128 | $0.00128 |
| Sonnet 5.5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
pull-request-template 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.
What it actually says
Pull Request 规范
用户要求创建 / 更新 PR（含「创建 pr」「提 PR」「改 PR 描述」）时：
- 先读取 仓库根目录
PULL_REQUEST_TEMPLATE.md，按其章节结构写 PR 标题与正文。 - 禁止只用 Cursor 默认的
## Summary/## Test plan两段式交差。 - 正文须包含模板中的区块（可按实际变更勾选，无内容的小节可写「无」或省略空 checkbox，但标题层级保持一致）：
# Pull Request: …标题行## 概要 (Overview)## 核心变更 (Key Changes)（功能新增 / UI·UX / 缺陷修复）## 变更清单 (Commit Log)（短 hash + 提交说明表）## 测试覆盖 (Testing)## 其他备注 (Notes)
- 按模板
[!IMPORTANT]：提交前更新tests/CHECKLIST.md中与本次变更对应的自动化测试清单，并在 PR 中注明已更新。 - 中文撰写；勾选已完成项用
[x]，待验证项保留[ ]。
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 First seen · 21 lines · 320 tokens per session scan A ed516ed888f8
pull-request-template is a cursor rule published in the GitHub repository RandyChen1985/nanzi-ai-agent-platform (209 stars, last pushed yesterday), licensed MIT. It adds 320 tokens to every session, about $0.0013 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
git-workflow
Cursor rule "git-workflow" from comet-ml/opik, covering git workflow, branch naming, commit format, pr title and pr body.
mstar-cursor-plan-mode
When using Cursor Plan mode with Morning Star, dual-write CreatePlan to .mstar/ harness artifacts and require per-task commits.
desktop-release-gate
Desktop app fixes must pass a local packaged build smoke test before pushing release tags or CI desktop builds.
branch-dev-main
Always develop on dev; merge to main after verified; keep both in sync.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.