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 fusengine/agents --skill astro-i18ngit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/astro-i18n)<a href="https://agentmods.dev/skills/fusengine/agents/astro-i18n"><img src="https://agentmods.dev/badge/skills/fusengine/agents/astro-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/fusengine/agents/astro-i18n"><img src="https://agentmods.dev/badge/skills/fusengine/agents/astro-i18n.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.01021 |
| Opus 5.5 | $0.00015 | $0.00408 |
| Sonnet 5.5 | $0.00008 | $0.00204 |
| Haiku 4.5 | $0.00004 | $0.00102 |
Grade A, and why
astro-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 1mo 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Also covers translating Content Collections per locale and adding hreflang alternate links via @astrojs/sitemap's i18n option for SEO. Does not cover general SEO meta tags beyond hreflang (astro-seo) or the Content Layer API itself (astro-content) — this skill focuses specifically on locale routing and URL generation.
Astro i18n
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Analyze existing routing, content collections, and locale files
- fuse-ai-pilot:research-expert - Verify latest Astro i18n docs via Context7/Exa
- mcp__context7__query-docs - Check
astro:i18nAPI and sitemap integration
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
When to Use
- Building multilingual Astro sites with locale-prefixed URLs
- Configuring
defaultLocaleand routing strategies - Generating locale-aware links with
getRelativeLocaleUrl() - Reading
Astro.currentLocalein components and pages - Adding
hreflangalternate links via@astrojs/sitemap - Translating content using Content Collections per locale
Built-in i18n (Astro 3.5+)
Astro's built-in i18n system provides:
- File-based locale routing via
src/pages/[locale]/ - Routing strategies for URL prefix behavior
- URL helper functions from
astro:i18n - Middleware-based routing logic
- Fallback locale configuration
Reference Guide
Concepts
| Topic | Reference | When to Consult |
|---|---|---|
| Routing config | routing-config.md | Setup and config options |
| Strategies | strategies.md | prefix-always vs prefix-other-locales |
| Helper functions | helper-functions.md | getRelativeLocaleUrl and all helpers |
| Content translation | content-translation.md | Translating content collections |
| Sitemap hreflang | sitemap-hreflang.md | SEO alternate links |
| Fallback | fallback.md | Missing translation fallback |
What ships with it
9 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.
- references/content-translation.md 2.4 KB
- references/fallback.md 1.8 KB
- references/helper-functions.md 3.6 KB
- references/routing-config.md 1.7 KB
- references/sitemap-hreflang.md 2.1 KB
- references/strategies.md 1.7 KB
- references/templates/i18n-config.md 1.9 KB
- references/templates/language-switcher.md 2.0 KB
- references/templates/locale-page.md 2.0 KB
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.
- 1mo ago Changed 81cfb1f4a715
- 1mo ago First seen · 92 lines · 38 tokens per session scan A 835240a54041
astro-i18n is a skill published in the GitHub repository fusengine/agents (34 stars, last pushed 14d ago), licensed MIT. It adds 38 tokens to every session and 1,021 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-08-30.
Other skills, from other repositories
improve-search-visibility-entity-footprint
Step of the improve-search-visibility playbook: checks the profiles answer engines read, plus local listings and reviews, against the brand's facts and writes corrections. Run improve-search-visibility instead; not for direct use.
radin-stats
Use for /radin-stats. Shows the stats or gain output of every companion tool that ships one, side by side.
ccpa-compliance
Analyze CCPA/CPRA obligations legally — applicability thresholds, consumer-rights procedures, notice at collection, the Do Not Sell or Share link, and service-provider contract terms. Use when the user needs to know whether CCPA applies and what their notices, request procedures and vendor contracts must say. Not for…
data-processing-agreement
Draft a GDPR Article 28 Data Processing Agreement — controller and processor roles, processing details, processor obligations, sub-processors, breach notice, audit rights, deletion and international transfers. Use when a customer asks the user to sign a DPA, or the user needs one for a vendor that handles their…
gdpr-compliance
Analyze GDPR obligations legally — data mapping, lawful basis, DPIA and DPO needs, data subject rights procedures, breach notification, transfer mechanisms and Article 30 records. Use when the user asks how to legitimize EU data transfers, whether they need a DPIA or DPO, or what GDPR legally requires of them. Not for…
compliance-monitor
Design a legal team's ongoing compliance oversight — monitoring scope per regulation, owners, escalation levels, board reporting and a compliance calendar. Use when the user needs to decide who owns each regulation, how non-compliance escalates and which legal deadlines to calendar. Not for automated control checks…