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/zhagqn/agentworkWrote 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/zhagqn/agentwork/anydoc)<a href="https://agentmods.dev/rules/zhagqn/agentwork/anydoc"><img src="https://agentmods.dev/badge/rules/zhagqn/agentwork/anydoc/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/zhagqn/agentwork/anydoc"><img src="https://agentmods.dev/badge/rules/zhagqn/agentwork/anydoc.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.00008 | $0.00099 |
| Opus 5.5 | $0.00003 | $0.00040 |
| Sonnet 5.5 | $0.00002 | $0.00020 |
| Haiku 4.5 | $0.00001 | $0.00010 |
Grade A, and why
anydoc 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
当任务需要读取办公文档或 PDF 时，按 .shared/skills/anydoc/SKILL.md 使用 anydoc。依赖只在项目级按需安装，禁止全局安装；输出写入 .tmp/anydoc/，保留原文件，默认不启用 hosted OCR；扫描 PDF 优先使用当前 agent 的视觉能力。
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 · 8 lines · 8 tokens per session scan A ed389d6ad674
anydoc is a cursor rule published in the GitHub repository zhagqn/agentwork (96 stars, last pushed 13d ago), licensed MIT. It adds 8 tokens to every session and 99 once invoked, about $0.0000 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-10.
Other cursor rules, from other repositories
sigma-reports
Build, validate, retrieve, and safely update Sigma report code representations through /v2/reports/spec. Use for fixed-layout or pixel-perfect reports, executive board packets, wide operational tables, invoices, statements, regulatory documents, and PDF delivery. Covers reusable report scaffolds, report pages…
citazioni
Citazioni corrette (stile numerico) e bibliografia coerente per tesi triennale in LaTeX.
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.