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/phuhao00/greatestworksWrote 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/phuhao00/greatestworks/p)<a href="https://agentmods.dev/rules/phuhao00/greatestworks/p"><img src="https://agentmods.dev/badge/rules/phuhao00/greatestworks/p/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/phuhao00/greatestworks/p"><img src="https://agentmods.dev/badge/rules/phuhao00/greatestworks/p.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.00350 | $0.00350 |
| Opus 5.5 | $0.00140 | $0.00140 |
| Sonnet 5.5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
p 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
Go项目开发规则
代码规范
- 遵循Go官方代码规范
- 使用gofmt格式化代码
- 变量命名使用驼峰命名法
- 常量使用大写字母和下划线
- 包名使用小写字母，简短有意义
错误处理
- 始终检查错误返回值
- 使用errors.New()或fmt.Errorf()创建错误
- 避免使用panic，除非是程序启动时的致命错误
- 使用defer进行资源清理
并发编程
- 使用goroutine处理并发任务
- 使用channel进行goroutine间通信
- 避免共享内存，使用通信来共享内存
- 使用sync包进行同步控制
性能优化
- 避免不必要的内存分配
- 使用对象池复用对象
- 合理使用缓存
- 避免在循环中进行重复计算
项目结构
- 遵循标准Go项目布局
- 按功能模块组织代码
- 使用internal包限制内部代码访问
- 合理使用接口和依赖注入
禁止使用的命令
- 不使用git checkout命令
- 不使用git reset命令
- 使用git switch切换分支
- 使用git restore恢复文件
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 · 46 lines · 350 tokens per session scan A 4996d4b4c841
p is a cursor rule published in the GitHub repository phuhao00/greatestworks (292 stars, last pushed 11mo ago), licensed MIT. It adds 350 tokens to every session, about $0.0014 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-09-01.
Other cursor rules, from other repositories
05-go-helpers
In a module whose go.mod requires x/rkit, use rkit before writing a small helper. Task → helper map and edge cases: x/rkit/README.md.
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
code-style
Formatting, lint, comments language.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.