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 integrate-ai-i18ngit 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/integrate-ai-i18n)<a href="https://agentmods.dev/skills/bosens-china/tc39-atlas/integrate-ai-i18n"><img src="https://agentmods.dev/badge/skills/bosens-china/tc39-atlas/integrate-ai-i18n/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/integrate-ai-i18n"><img src="https://agentmods.dev/badge/skills/bosens-china/tc39-atlas/integrate-ai-i18n.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.00092 | $0.00855 |
| Opus 5 | $0.00046 | $0.00428 |
| Sonnet 5 | $0.00018 | $0.00171 |
| Haiku 4.5 | $0.00009 | $0.00085 |
Grade A, and why
integrate-ai-i18n 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate ai-i18n
Preserve the project's package manager, Vite plugins, framework conventions, and configuration style.
Read product documentation
Read https://bosens-china.github.io/ai-i18n/llms.txt, select the pages that match the current
framework and requested capability, and read only those pages. Use llms-full.txt only when the
index or targeted pages are unavailable; do not load the full corpus by default.
User-facing installation steps, configuration fields, Runtime APIs, framework examples, generated files, and troubleshooting live in that documentation. Do not reproduce or infer those details from this Skill. If deployed documentation conflicts with the target project's installed types, source, or executable behavior, follow the target project and report the discrepancy.
Inspect the target build
Read the target app's package.json, vite.config.*, TypeScript config, entry files, and framework
plugin setup. Confirm that the app matches the current public support requirements before editing it.
In a monorepo, identify one target Vite build. Ask the user only when more than one app is plausible, or when a new setup has no source and target language decision that can be inferred from existing configuration. Preserve configured values.
Use one @ai-i18n/vite registration, one framework mode, and one i18n directory per Vite build.
Treat reachable local workspace source as part of the consuming build. Do not create a separate
integration for a source-only package or rewrite CommonJS as an incidental migration.
If an existing overrides.json contains file-scoped rules, preserve its exact normalized POSIX paths
relative to this Vite root; never rewrite them to machine-specific absolute paths during integration.
Do not enable optional behavior by default. Keep explicit imports and omit automatic translation, automatic imports, language persistence, locale loading, cache cleanup, HTML extraction, ESLint, and test integration unless the user requests them. Do not remove an optional feature that is already configured. When an optional feature is requested, read Agent defaults for optional features and the matching public documentation page.
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.
- 11d ago First seen · 69 lines · 92 tokens per session scan A 75b961866d93
integrate-ai-i18n is a skill published in the GitHub repository bosens-China/tc39-atlas (0 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 855 once invoked, about $0.0005 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
photo-sphere-viewer
Use when displaying 360-degree panoramic images (equirectangular/cubemap/dual-fisheye) in web applications, building virtual tours with markers and transitions, embedding interactive panoramas in Vue/React/vanilla JS, or creating 360-degree video players with gyroscope VR support. Photo-Sphere-Viewer v5: JavaScript…
angular-developer
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component…
angular-new-app
Creates a new Angular app using the Angular CLI. This skill should be used whenever a user wants to create a new Angular application and contains important guidelines for how to effectively create a modern Angular application.
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
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…
ax-ai
This skill helps an LLM generate correct AI provider setup and configuration code using @ax-llm/ax. Use when the user asks about ai(), providers, models, routing, adaptive balancing, presets, embeddings, batch audio with ai.transcribe() or ai.speak(), extended thinking, context caching, or mentions…