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/baizhiheizi/enjoy_player/docs-systemgit clone --depth 1 https://github.com/baizhiheizi/enjoy_playerWrote 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/baizhiheizi/enjoy_player/docs-system)<a href="https://agentmods.dev/rules/baizhiheizi/enjoy_player/docs-system"><img src="https://agentmods.dev/badge/rules/baizhiheizi/enjoy_player/docs-system.svg" alt="Measured on agentmods" 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 | $0.00130 | $0.00130 |
| Opus 5 | $0.00065 | $0.00065 |
| Sonnet 5 | $0.00026 | $0.00026 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
docs-system 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 4d 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 AGPL-3.0
The repository is licensed AGPL-3.0, 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.
- 4d ago First seen · 12 lines · 130 tokens per session scan A 8a2028299d33
docs-system is a cursor rule published in the GitHub repository baizhiheizi/enjoy_player (10 stars, last pushed today), licensed AGPL-3.0. It adds 130 tokens to every session, about $0.0006 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-31.
Other cursor rules, from other repositories
plan-execution-loop
Execute a docs/plans/.md slice with subagent implement → evidence-based audit → fix until 90+ — invoke manually when running a plan.
plan-feature
Framework for planning a new feature end-to-end — use when asked to plan or design a new module.
refactor-large-files
Guidance for splitting large route files into maintainable pieces.
frontend-forms
Form submission and error display patterns — toast vs Alert, batch() in try/catch, field-level errors.
frontend-lib
Patterns for frontend lib files — API client, auth, constants, utilities.
go-service-errors
Go service error translation, nullable TIMESTAMPTZ scans, history, and side effects.