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.
npx skills add hashiiiii/rules-for-ai --skill hashiiiii-localegit clone --depth 1 https://github.com/hashiiiii/rules-for-aiWrote 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/skills/hashiiiii/rules-for-ai/hashiiiii-locale)<a href="https://agentmods.dev/skills/hashiiiii/rules-for-ai/hashiiiii-locale"><img src="https://agentmods.dev/badge/skills/hashiiiii/rules-for-ai/hashiiiii-locale/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/skills/hashiiiii/rules-for-ai/hashiiiii-locale"><img src="https://agentmods.dev/badge/skills/hashiiiii/rules-for-ai/hashiiiii-locale.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.00027 | $0.00932 |
| Opus 5 | $0.00014 | $0.00466 |
| Sonnet 5 | $0.00005 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
hashiiiii-locale 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 11d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Locale Setup
Set locale preferences at the scope that the user selects. Do not use the plugin installation scope to select the locale scope.
Scope Selection
Accept user, project, or local as a bare argument. Also accept scope=<scope>.
If the request has no scope, ask for the scope first. Then ask for the locale values.
Do not infer the scope from the current directory or plugin installation.
Before each write, state the selected scope, exact target path, and sharing behavior.
| Scope | Target | Sharing behavior |
|---|---|---|
user |
${XDG_CONFIG_HOME:-${HOME:-}/.config}/rules-for-ai/LOCALE.md |
Use the locale in all projects for this user. |
project |
<repo>/.rules-for-ai/LOCALE.md |
Commit the locale for team use. |
local |
<absolute-git-dir>/rules-for-ai/LOCALE.md |
Use the locale in this Git worktree, outside git status. |
For project or local, use git rev-parse --show-toplevel to find the repository.
If the command fails, stop without a write.
For local, get <absolute-git-dir> from git rev-parse --absolute-git-dir. This path keeps linked worktree preferences separate.
Do not commit a project file automatically. Do not add a local file to .gitignore or .git/info/exclude.
Resolution Order
The first existing file wins as a whole:
<absolute-git-dir>/rules-for-ai/LOCALE.md<repo>/.rules-for-ai/LOCALE.md${XDG_CONFIG_HOME:-${HOME:-}/.config}/rules-for-ai/LOCALE.md- Bundled
LOCALE.default.md - Inline
en_USvalues
Project instructions in CLAUDE.md or AGENTS.md take precedence over the resolved locale keys.
Locale Arguments
- A single POSIX-style tag, such as
ja_JP, sets all five keys. - Key-value arguments set separate keys.
- If the request has no locale values, ask about each artifact after scope selection.
| Key | Artifact |
|---|---|
issues |
Issues |
pull-requests |
Pull requests |
comments |
Code comments |
logs |
Log messages |
test-logs |
Test log messages |
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.
- 11d ago First seen · 107 lines · 27 tokens per session scan A 443f249894ea
hashiiiii-locale is a skill published in the GitHub repository hashiiiii/rules-for-ai (10 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 932 once invoked, about $0.0001 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.
Other skills, from other repositories
iflytek-text-proofread
A tool that checks Chinese writing through iFlytek’s official document-proofreading service. It looks for spelling, punctuation, wording, factual, terminology, and sensitive-content problems.
iflytek-translate
A text-translation tool that uses iFlytek's machine-translation service and supports more than 70 language pairs. It can translate text supplied directly, through standard input, or from a file.
iflytek-video-translate
A tool that translates a video’s speech into another language and creates dubbed audio. Video localization means adapting video content for viewers who speak a different language.
yida-i18n
A tool for managing the languages and translated text in YiDA applications, including which languages are enabled and the wording shown on pages.
aso-marketing
Optimize App Store and Google Play listings via a 7-phase, plan-approval-gated ASO workflow (keyword strategy, metadata, localization). Don't use for web SEO, paid UA campaigns, or pre-submission compliance audits.
azure-translator
Expert knowledge for Azure Translator development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using translate/detect/dictionary APIs, Custom Translator, glossaries, document jobs, or Docker containers…