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/encoding)<a href="https://agentmods.dev/rules/yuz9610/poe2overlay/encoding"><img src="https://agentmods.dev/badge/rules/yuz9610/poe2overlay/encoding/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/encoding"><img src="https://agentmods.dev/badge/rules/yuz9610/poe2overlay/encoding.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
encoding 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
Encoding conventions
Read docs/ENCODING.md for the full policy and tooling matrix.
When creating or editing files in this repo:
- Use UTF-8 without BOM for
.rs,.ts,.tsx,.js,.mjs,.json,.html,.css,.md,.toml,.ps1, and everything underdata/. - Run PowerShell scripts only with PowerShell 7+ (
pwsh); do not target Windows PowerShell 5.1. New.ps1files should include#Requires -Version 7.0and dot-sourcescripts/_InitializeUtf8Console.ps1after theparamblock. - Do not save Chinese (or any) text as GBK, Big5, or system ANSI.
- Do not enable encoding auto-guess; preserve existing UTF-8 bytes in
data/*.jsonso area names matchClient.txtexactly. - Line endings: LF for all files including
.ps1; only.bat/.cmduse CRLF (per.editorconfig). - Node scripts: read/write with
"utf8"; strip a leading BOM with.replace(/^\uFEFF/, "")when reading JSON if needed. - Rust already assumes UTF-8 for
read_to_stringandfrom_utf8_lossyon logs; do not introduce other encodings without explicit project approval.
If a file shows mojibake or `` replacement characters, stop and fix encoding before editing content.
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 · 21 lines · 350 tokens per session scan A b34813e1480e
encoding is a cursor rule published in the GitHub repository yuz9610/POE2Overlay (9 stars, last pushed 4mo 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-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).