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/yuz9610/POE2OverlayWrote 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/yuz9610/poe2overlay/docs-sync)<a href="https://agentmods.dev/rules/yuz9610/poe2overlay/docs-sync"><img src="https://agentmods.dev/badge/rules/yuz9610/poe2overlay/docs-sync/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/yuz9610/poe2overlay/docs-sync"><img src="https://agentmods.dev/badge/rules/yuz9610/poe2overlay/docs-sync.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.00831 | $0.00831 |
| Opus 5.5 | $0.00332 | $0.00332 |
| Sonnet 5.5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
docs-sync 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation sync
When you add a feature, change behavior, or rename/remove user-visible or architectural surfaces, update the matching docs in the same change (same PR / session). Do not leave code and docs out of sync.
Canonical matrix: docs/ARCHITECTURE.md § 文檔同步.
Docs ownership / target architecture: docs/README.md § 目標信息架構.
Quick checklist
| Change type | Update at minimum |
|---|---|
| New/changed Tauri command or event | lib.rs, src/api/tauri.ts, types.ts if needed, ARCHITECTURE.md IPC tables |
| New UI panel, shortcut, setting | USER_GUIDE.md, ARCHITECTURE.md (modules / 常見修改入口), SettingsPanel area in ARCHITECTURE if new setting key |
New/changed data/ schema or file |
BUILD_JSON.md or README data section, ARCHITECTURE.md data table, example JSON if applicable |
| Build JSON AI workflow or prompt template | CREATE_BUILD.md; BUILD_JSON.md if schema changes |
| New Rust module or major frontend folder | ARCHITECTURE.md directory / module tables |
| Dev workflow (scripts, npm/cargo commands) | ARCHITECTURE.md, README.md, PROJECT_WORKFLOW.md, AGENTS.md if agent-facing |
| Task / sprint / commit workflow | 先 PROJECT_WORKFLOW.md；再 AI_AGENT_PROMPTS.md 開頭、AGENTS.md、CLAUDE.md、AI_AGENT_SETUP.md、workflow.mdc；SPRINTS.md、sprints/README.md（SUMMARY 模板）、task docs |
| Encoding / tooling policy | ENCODING.md, .cursor/rules/encoding.mdc |
New doc file under docs/ |
docs/README.md index / target architecture; new file starts with 文檔目的 / 不負責 |
| Docs information architecture / SOT ownership | 先 docs/README.md § 目標信息架構；再 AGENTS.md、.cursor/rules/architecture.mdc、this file if agent-facing |
Rules
- Same change: code + docs together; mention doc updates in the summary.
- No orphan docs: if removing a feature, remove or update stale sections (grep doc filenames for old command/event names).
- One source of truth: IPC lists live in ARCHITECTURE.md; AGENTS.md / cursor rules only summarize—update ARCHITECTURE first when IPC changes.
- User vs dev: player-facing text → USER_GUIDE; architecture/IPC → ARCHITECTURE; JSON schema → BUILD_JSON.
- Workflow state: idea/task/sprint transitions live in PROJECT_WORKFLOW.md; prompt templates live in AI_AGENT_PROMPTS.md. Follow the workflow state transition table before editing
BRAINSTORM.md,SPRINTS.md, task docs, or sprint summaries. - Purpose block: every
docs/**/*.mdshould state its文檔目的and what it does not own near the top. - No long duplication: if content belongs to another SOT, link to it instead of copying long rules or tables.
- Skip only when: pure internal refactor with zero behavior/API/UI/data change (state explicitly: "no doc updates needed").
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 · 42 lines · 831 tokens per session scan A d12fa6fe7999
docs-sync is a cursor rule published in the GitHub repository yuz9610/POE2Overlay (9 stars, last pushed 4mo ago), licensed MIT. It adds 831 tokens to every session, about $0.0033 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-31.
Other cursor rules, from other repositories
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).