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 agentmods add skills/conectlens/lenserfight/apps-language-rulesnpx skills add conectlens/lenserfight --skill apps-language-rulesgit clone --depth 1 https://github.com/conectlens/lenserfightWrote 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/conectlens/lenserfight/apps-language-rules)<a href="https://agentmods.dev/skills/conectlens/lenserfight/apps-language-rules"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/apps-language-rules.svg" alt="Measured on agentmods" 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.00060 | $0.01442 |
| Opus 5 | $0.00030 | $0.00721 |
| Sonnet 5 | $0.00012 | $0.00288 |
| Haiku 4.5 | $0.00006 | $0.00144 |
Grade A, and why
apps-language-rules 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 6d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apps Language Rules
Use when
- Adding new UI strings to
apps/web(must add toen.json+tr.jsonstubs) - Writing new documentation pages (English first; Turkish stub in
docs/tr/recommended) - Adding a new locale beyond
en/tr - Checking consistency of translations across JSON catalogs
- Setting up
hreflangSEO for multilingual pages - Reviewing React components for hardcoded strings that bypass i18next
Supported languages
| Code | Name | Default? | App locale files | Docs status |
|---|---|---|---|---|
en |
English | ✅ Yes | en.json |
Complete |
tr |
Türkçe | No | tr.json |
WIP |
es |
Español | No | not yet | Stub |
fr |
Français | No | not yet | Stub |
de |
Deutsch | No | not yet | Stub |
zh |
中文 | No | not yet | Stub |
ja |
日本語 | No | not yet | Stub |
ko |
한국어 | No | not yet | Stub |
ru |
Русский | No | not yet | Stub |
pt |
Português | No | not yet | Stub |
it |
Italiano | No | not yet | Stub |
All codes are registered in supabase/seeds/01_core_languages.sql and configured as VitePress locales in apps/docs/.vitepress/config.ts. Adding app locale JSON files is the primary contribution needed.
Forum i18n (apps/web — React + i18next)
Setup
- i18next initialised in
apps/web/src/i18n.ts - Locale files:
apps/web/src/locales/en.jsonandapps/web/src/locales/tr.json - Imported at app entry (
apps/web/src/index.tsx) before<App /> - Language detection order:
localStorage(lf-languagekey) → browser navigator → html tag - Fallback: English
Rules for adding strings
- Add key to
en.json(English, authoritative). - Add same key to
tr.jsonwith Turkish translation or""placeholder. - Use
useTranslation()hook in React components:const { t } = useTranslation(). - Never hardcode user-facing strings in JSX — always use
t('namespace.key'). - Use interpolation for dynamic values:
t('prompts.usedTimes', { count: n }).
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 120 lines · 60 tokens per session scan A 3890e5328f3a
apps-language-rules is a skill published in the GitHub repository conectlens/lenserfight (19 stars, last pushed 26d ago), licensed MIT. It adds 60 tokens to every session and 1,442 once invoked, about $0.0003 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-30.
Other skills, from other repositories
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.
i18n
Règle 09 : Internationalisation (i18n). Use when implementing internationalization.
i18n
Audit internationalization coverage and find hardcoded strings. Use when user asks to "check i18n", "/i18n", "find hardcoded strings", "check translations", or wants to verify translation coverage. Don't use for backend string extraction, non-frontend code, projects without an i18n library, accessibility (use…
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
generic-fullstack-code-reviewer
Review full-stack code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md compliance. Enforces TypeScript strict mode, input validation, GPU-accelerated animations, and design system consistency. Use when completing features, before commits, or reviewing pull requests.