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 bosens-China/tc39-atlas --skill use-ai-i18n-mcpgit clone --depth 1 https://github.com/bosens-China/tc39-atlasWrote 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/bosens-china/tc39-atlas/use-ai-i18n-mcp)<a href="https://agentmods.dev/skills/bosens-china/tc39-atlas/use-ai-i18n-mcp"><img src="https://agentmods.dev/badge/skills/bosens-china/tc39-atlas/use-ai-i18n-mcp/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/bosens-china/tc39-atlas/use-ai-i18n-mcp"><img src="https://agentmods.dev/badge/skills/bosens-china/tc39-atlas/use-ai-i18n-mcp.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.00132 | $0.01110 |
| Opus 5 | $0.00066 | $0.00555 |
| Sonnet 5 | $0.00026 | $0.00222 |
| Haiku 4.5 | $0.00013 | $0.00111 |
Grade A, and why
use-ai-i18n-mcp 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use ai-i18n MCP
Use the locate → list → update → verify workflow. Do not scan for i18n directories or edit generated files manually while the MCP tools are available.
Read the right source
For user-facing registration, product behavior, generated-file guidance, or integration
troubleshooting, read https://bosens-china.github.io/ai-i18n/llms.txt and then the one relevant page.
Do not load llms-full.txt by default or duplicate that guidance in this Skill.
For MCP calls, read Tool contracts before the first call. It is the
Agent-only authority for message identity, inputs, pagination, batch behavior, write boundaries, and
authorization. Read Error recovery only after a returned next_action is
insufficient or when a tool or protocol file is unavailable.
Locate the target app
- Identify the Vite app the user wants to change. In a monorepo, do not treat the repository root
or a similarly named
i18n/directory as the target. - Read the app's
package.json, package scripts, andvite.config.*as text. Do not execute the Vite config. - Resolve Vite
rootfrom the command's working directory. Resolve a relativeaiI18n({ directory })against that root; use an absolutedirectoryunchanged. The default directory isi18n. - Pass the resulting absolute path as
i18n_directory.
If more than one Vite app is plausible, ask the user which app to use before calling MCP.
The app's framework mode and autoImport setting affect source integration but do not change the MCP
directory contract. Do not add or remove Runtime imports as part of a translation-only MCP task.
When package installation, Vite configuration, or Runtime source integration is incomplete or
requested, use the integrate-ai-i18n Skill before starting this translation workflow.
The selected app's extracted set includes every reachable local workspace source processed by that
Vite build. Treat source-only packages as source_files within the consuming app, not as separate MCP
targets. Never point two Vite builds at one i18n directory; call the tools once per selected app.
Use tool-returned source_file values; never decode or guess a source path from a physical filename.
What ships with it
3 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.
- 11d ago First seen · 79 lines · 132 tokens per session scan A 196481195553
use-ai-i18n-mcp is a skill published in the GitHub repository bosens-China/tc39-atlas (0 stars, last pushed today), licensed MIT. It adds 132 tokens to every session and 1,110 once invoked, about $0.0007 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
build-with-tinybase
Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase. Use when choosing TinyBase for in-memory tabular or key-value state, generating an app with create-tinybase, adding schemas or UI bindings, configuring browser or database persistence, configuring MergeableStore…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
record-upgrade-instructions
Record upgrade instructions alongside a Prisma 8 breaking-change PR, so downstream consumers (users of @internal/ and authors of Prisma 8 extensions) can apply the matching code translation automatically via the published upgrade skills. Use when you have refactored framework code and the test suite went red in…
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.