encoding

A project rulebook for storing text files as UTF-8 without a byte-order mark and using the expected line endings. UTF-8 is a widely used way to represent text, while line endings mark where each line stops.

In plain words
What is it for?
Use it whenever creating or editing source code, documentation, data, or PowerShell scripts in the project. It also defines how to read and write JSON and which PowerShell version to use.
Why use it?
It prevents garbled characters, inconsistent files, and scripts that behave differently across operating systems. It also makes sure existing text data is not silently changed by encoding conversion.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/yuz9610/poe2overlay/encoding
Clone the repo
git clone --depth 1 https://github.com/yuz9610/POE2Overlay

Made for: Cursor.

Per session 350 This file is loaded in full into every session.
When invoked 350 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00350 $0.00350
Opus 5 $0.00175 $0.00175
Sonnet 5 $0.00070 $0.00070
Haiku 4.5 $0.00035 $0.00035

Measured 2d ago against content hash b34813e1480e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.cursor/rules/encoding.mdc · 21 lines

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 under data/.
  • Run PowerShell scripts only with PowerShell 7+ (pwsh); do not target Windows PowerShell 5.1. New .ps1 files should include #Requires -Version 7.0 and dot-source scripts/_InitializeUtf8Console.ps1 after the param block.
  • 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/*.json so area names match Client.txt exactly.
  • Line endings: LF for all files including .ps1; only .bat / .cmd use 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_string and from_utf8_lossy on 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.

Changes

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.

  1. 2d ago First seen · 21 lines · 350 tokens per session scan A b34813e1480e

Subscribe to this mod's changes

encoding is a cursor rule published in the GitHub repository yuz9610/POE2Overlay (8 stars, last pushed 3mo ago), licensed MIT. It adds 350 tokens to every session, about $0.0018 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.