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/.claude/skills/intlayer-dev-tools/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-dev-tools)<a href="https://agentmods.dev/skills/aymericzip/intlayer/intlayer-dev-tools"><img src="https://agentmods.dev/badge/skills/aymericzip/intlayer/intlayer-dev-tools/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-dev-tools"><img src="https://agentmods.dev/badge/skills/aymericzip/intlayer/intlayer-dev-tools.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.00080 | $0.00705 |
| Opus 5.5 | $0.00032 | $0.00282 |
| Sonnet 5.5 | $0.00016 | $0.00141 |
| Haiku 4.5 | $0.00008 | $0.00071 |
Grade A, and why
intlayer-dev-tools 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- intlayer-dev-tools — 92% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intlayer Dev Tools
Lint (ESLint / oxlint)
eslint-plugin-intlayer catches hardcoded strings, dynamic calls the Intlayer compiler cannot optimize, and unused dictionary content.
npm install --save-dev eslint-plugin-intlayer
Then spread intlayer.configs.recommended in your eslint.config.mjs (oxlint is also supported).
| Config | no-raw-text |
static-dictionary-key |
no-dynamic-field-access |
|---|---|---|---|
recommended |
warn | error | error |
strict |
error | error | error |
contract-only |
off | error | error |
Language Server (LSP)
@intlayer/lsp (binary intlayer-lsp) brings Go-to-Definition from a useIntlayer("key") call to its .content file, Find References, hover previews, key autocompletion and diagnostics.
npm install --save-dev @intlayer/lsp
VS Code Extension
Jump from a dictionary key to its content file, extract content from a component, and run build, fill, test, push and pull from the command palette.
MCP Server
Gives AI assistants access to the Intlayer documentation and CLI.
npx intlayer init mcp
This writes the MCP configuration for your IDE (local @intlayer/mcp over stdio, or the hosted https://mcp.intlayer.org).
A WebMCP is also available for the main website and documentation at https://intlayer.org.
CI/CD
Fill missing translations with AI on each change, and fail the build on missing ones:
npx intlayer fill --git-diff --mode complete
npx intlayer test
Chrome Extension
Inspect the i18n setup of any website: framework, i18n library, locales, hreflang and SEO tags.
References
Tools
What ships with it
7 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 · 83 lines · 80 tokens per session scan A abe80e200d30
intlayer-dev-tools is a skill published in the GitHub repository aymericzip/intlayer (841 stars, last pushed today), licensed Apache-2.0. It adds 80 tokens to every session and 705 once invoked, about $0.0003 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
agent-browser
Use the agent-browser CLI to exercise web interfaces, inspect rendered accessibility state, verify interactions, and capture screenshots. Use for browser-based UI testing and evidence collection. Do not use as a substitute for deterministic Playwright coverage when an automated regression test is the requested…
output-dev-eval-testing
Create offline evaluation tests for Output SDK workflows using @outputai/evals. Use when implementing test evaluators with verify(), creating dataset YAML files, building eval workflows, or running workflow tests via CLI.
output-meta-project-context
Comprehensive guide to Output.ai Framework for building durable, LLM-powered workflows orchestrated by Temporal. Covers project structure, workflow patterns, steps, LLM integration, HTTP clients, CLI commands, and the full inventory of available agents and skills.
output-build-workflow
Implement an Output SDK workflow from a plan document. Use when the user asks to build, implement, or code a workflow from an existing plan, or after output-plan-workflow has produced a plan and the user is ready to build.
output-dev-create-skeleton
Generate workflow skeleton files using the Output SDK CLI. Use when starting a new workflow, scaffolding project structure, or understanding the generated file layout.
output-dev-folder-structure
Workflow folder structure conventions for Output SDK. Use when creating new workflows, organizing workflow files, or understanding the standard project layout.