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/workflow)<a href="https://agentmods.dev/rules/yuz9610/poe2overlay/workflow"><img src="https://agentmods.dev/badge/rules/yuz9610/poe2overlay/workflow/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/workflow"><img src="https://agentmods.dev/badge/rules/yuz9610/poe2overlay/workflow.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.00653 | $0.00653 |
| Opus 5.5 | $0.00261 | $0.00261 |
| Sonnet 5.5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
workflow 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow enforcement
Canonical (edit here first): docs/PROJECT_WORKFLOW.md § Agent 強制規則.
Prompts: docs/AI_AGENT_PROMPTS.md. Human cheat sheet: docs/AI_AGENT_SETUP.md.
Docs ownership: docs/README.md. Workflow rules belong here in PROJECT_WORKFLOW.md; this rule is summary only.
When the user uses a workflow short command, follow the matching step in AI_AGENT_PROMPTS.md. Do not improvise a shorter path.
Five hard rules (summary only — do not expand here)
- First response = proposal only (read-only exploration OK). No writes, no commit, no
Done. - Skip gate only if the user says in the same message:
跳过确认/跳過確認/skip confirmation/直接修改/直接执行/直接實作/不用等确认/不必等確認. Vague urgency orIn progress/Planneddoes not skip. 執行 task→ Phase A execution plan first; Phase B after human confirms.In progressdoes not skip Phase A.- Step 4 never commits.
驗收 task→ acceptance review first; agent readslogs/*.log; commit only after human confirms Accept (plus log downgrade). - Changing workflow rules → update
PROJECT_WORKFLOW.mdfirst, then syncAI_AGENT_PROMPTS.mdintro,AGENTS.md,AI_AGENT_SETUP.md, this file.
Step 4 / Step 5 pointers
| Step | First reply | After confirm |
|---|---|---|
| 4 Execute | Plan only | Implement; fill task doc; no commit |
| 5 Accept | Accept / Needs changes / Blocked |
Done + commit per § Commit Message; Co-authored-by: CursorAgent; Windows git commit -F UTF-8 |
Step 3: new sprint → SPRINTS.md Current Sprint only (Planned). Step 6: SUMMARY.md per sprints/README.md § SUMMARY template; handoff IDs must exist in SPRINTS.md Task List; include workflow / project / docs review; update SPRINTS.md Current Snapshot, parent item status, Task List status / sprint fields, and reorder Above The Line Items / Task List with the same item order (in progress / started, then not started, then done); send larger improvements back to brainstorm / review / planning.
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 · 30 lines · 653 tokens per session scan A e458d8bb3c39
workflow is a cursor rule published in the GitHub repository yuz9610/POE2Overlay (9 stars, last pushed 4mo ago), licensed MIT. It adds 653 tokens to every session, about $0.0026 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).