Borrowing it
Nothing to install: this file belongs to aymericzip/intlayer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aymericzip/intlayer/main/.agents/skills/intlayer-lit/SKILL.mdgit clone --depth 1 https://github.com/aymericzip/intlayerWrote 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/aymericzip/intlayer/intlayer-lit)<a href="https://agentmods.dev/skills/aymericzip/intlayer/intlayer-lit"><img src="https://agentmods.dev/badge/skills/aymericzip/intlayer/intlayer-lit/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/aymericzip/intlayer/intlayer-lit"><img src="https://agentmods.dev/badge/skills/aymericzip/intlayer/intlayer-lit.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.00051 | $0.00872 |
| Opus 5.5 | $0.00020 | $0.00349 |
| Sonnet 5.5 | $0.00010 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
intlayer-lit 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 16d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- intlayer-lit — 100% identical, 4 lines differ
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.
Intlayer Lit Usage
Core Philosophy
Intlayer promotes Component-Level Content Declaration. Instead of a massive global translation file, content is declared in *.content.ts files adjacent to the Lit elements that use them.
Workflow
To create a translated element, you need two files:
- Declaration: A content file (e.g.,
myElement.content.ts) defining the dictionary. - Implementation: A
LitElement(e.g.,my-element.ts) using theuseIntlayercontroller.
Declare Content
Create a content file using t() for translations.
File: src/components/myElement.content.ts
import { t, type Dictionary } from "intlayer";
const content = {
// The 'key' must be unique and matches what you pass to useIntlayer()
key: "my-element",
content: {
title: t({
en: "Welcome",
fr: "Bienvenue",
es: "Hola",
}),
},
} satisfies Dictionary;
export default content;
Setup
Call installIntlayer() from lit-intlayer before any custom element is registered (see the Vite and Lit guide).
useIntlayer Controller
[!IMPORTANT] In Lit,
useIntlayertakes the host element as first argument. It registers itself as aReactiveController, so the element re-renders automatically when the locale changes.
import { LitElement, html } from "lit";
import { customElement } from "lit/decorators.js";
import { useIntlayer } from "lit-intlayer";
@customElement("my-element")
export class MyElement extends LitElement {
private content = useIntlayer(this, "my-element");
override render() {
return html`
<h1>${this.content.title}</h1>
<!-- Return string (.value) for native attributes -->
<img alt=${this.content.title.value} />
`;
}
}
useLocale Controller
import { useLocale } from "lit-intlayer";
// Inside a LitElement
private locale = useLocale(this);
// this.locale.locale, this.locale.availableLocales, this.locale.setLocale("fr")
What ships with it
8 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.
- 16d ago Changed · +4 lines 0b3f8f2eea9a
- 22d ago First seen · 116 lines · 51 tokens per session scan A f678becb7c33
intlayer-lit is a skill published in the GitHub repository aymericzip/intlayer (851 stars, last pushed 4d ago), licensed Apache-2.0. It adds 51 tokens to every session and 872 once invoked, about $0.0002 per session on Opus 5.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-09-24.
Other skills, from other repositories
webiny-v5-to-v6-migration
Migration patterns for converting v5 Webiny code to v6 architecture. Use this skill when migrating existing v5 plugins to v6 features, converting context plugins to DI services, adapting v5 event subscriptions to v6 EventHandlers, or understanding how v5 patterns translate to v6. Targeted at AI agents performing…
next-intl-i18n
Implement, migrate, or debug next-intl in a Next.js App Router project. Use when a change touches a locale URL, proxy, request config, message file, ICU message, formatted number, date, or list, RTL or CJK layout, localized CMS content, a locale switcher, or a translated error page. For canonicals, hreflang, sitemaps…
nextjs-seo-international
Multilingual SEO for a Next.js site. Use for hreflang, es versus es-MX, one URL per language, partly translated content, translated titles and descriptions, machine translation quality, the locale switcher as a crawl path, and market launches. For a locale that is not indexed at all start with nextjs-seo-technical…
localize-page
Convert or refactor Solana.com monorepo pages and their directly owned components to the repository's shared i18n system. Use when asked to internationalize, localize, remove hard-coded user-facing copy from, add translations to, or audit a page or route in apps/web, apps/docs, apps/media, apps/templates…
use-ai-i18n-mcp
Use the eight local ai-i18n MCP tools to inspect missing or orphaned translations, update the configured JSON or SQLite Translation Memory, and manage reviewed overrides.json values. Use when working with aii18nlisttranslations, aii18nsettranslations, aii18ncleartranslations, aii18nlistorphanmessages…
integrate-ai-i18n
Integrate ai-i18n into Vite browser projects that use Vue 3, React 18+, or vanilla JavaScript and TypeScript. Use when installing or configuring @ai-i18n/vite, adding translation calls or virtual:ai-i18n imports, selecting framework mode, enabling auto imports or ESLint, configuring optional locale loading or LLM…