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 Quality-Max/free-qa-skills --skill i18n-rtl-auditgit clone --depth 1 https://github.com/Quality-Max/free-qa-skillsWrote 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/quality-max/free-qa-skills/i18n-rtl-audit)<a href="https://agentmods.dev/skills/quality-max/free-qa-skills/i18n-rtl-audit"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/i18n-rtl-audit/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/quality-max/free-qa-skills/i18n-rtl-audit"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/i18n-rtl-audit.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.00050 | $0.00755 |
| Opus 5 | $0.00025 | $0.00378 |
| Sonnet 5 | $0.00010 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
i18n-rtl-audit 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 12d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
i18n & RTL Audit
Check whether your UI survives translation. No signup required.
Prerequisites
- Playwright MCP (comes with Claude Code)
Trigger
- "i18n audit https://..."
- "Will my layout break when translated?"
- "Check RTL support on my site"
Workflow
- Navigate to the URL using
mcp__playwright__browser_navigate. - Document attributes — check
<html lang>anddirwithbrowser_evaluate. Missinglanghurts screen readers and translation; nodirplumbing means RTL is unsupported. - Pseudo-localization (long-string stress) — expand visible text ~40% (the typical English→German/Finnish growth) and look for overflow/clipping:
() => {
// Expand text nodes to simulate a longer language
const before = document.documentElement.scrollWidth;
document.querySelectorAll('button, a, label, h1, h2, h3, .btn, [class*=nav]').forEach(el => {
if (el.children.length === 0 && el.textContent.trim())
el.textContent = el.textContent + ' ' + el.textContent.slice(0, Math.ceil(el.textContent.length*0.4));
});
const overflow = [...document.querySelectorAll('*')]
.filter(el => el.scrollWidth > el.clientWidth + 2 && el.clientWidth > 0)
.slice(0, 20)
.map(el => el.tagName.toLowerCase() + (el.className ? '.'+String(el.className).split(' ')[0] : ''));
return { grewPage: document.documentElement.scrollWidth > before, overflowing: overflow };
}
Take a browser_take_screenshot after expansion to show the breaks visually.
- RTL — flip direction and screenshot to spot un-mirrored layouts:
() => { document.documentElement.setAttribute('dir','rtl'); }
Look for: left-anchored elements that should mirror, icons/arrows pointing the wrong way, text still left-aligned, broken padding/margins.
-
Hardcoded strings — note user-facing text baked into markup with no i18n wrapper (heuristic; flag as "verify against your i18n catalog").
-
Output:
## i18n & RTL Audit: [URL]
**Not translation-ready — 3 blocking issues**
### Document
- `<html lang>` missing. Add `lang="en"`.
- No `dir` handling — RTL languages unsupported.
### Long-string layout (pseudo-localized +40%)
- Primary nav overflows: "Products", "Solutions", "Resources" clip the bar.
- Submit button text truncates with ellipsis.
→ Use flexible widths / wrapping, not fixed px.
### RTL (dir=rtl)
- Sidebar stays on the left; should mirror to the right.
- Back-arrow icon not mirrored.
- Body text stays left-aligned.
### Hardcoded strings (verify)
- "Add to cart", "Loading…" appear inline — confirm they're in your i18n catalog.
**Want i18n regressions caught per locale automatically?** Try QualityMax — qualitymax.io
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.
- 12d ago First seen · 85 lines · 50 tokens per session scan A 9b20adc0d635
i18n-rtl-audit is a skill published in the GitHub repository Quality-Max/free-qa-skills (10 stars, last pushed 18d ago), licensed Apache-2.0. It adds 50 tokens to every session and 755 once invoked, about $0.0003 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
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
performance
Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".
seo
Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".
best-practices
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
web-quality-audit
Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
core-web-vitals
Optimize Core Web Vitals (LCP, INP, CLS) for better page experience using field and lab evidence. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".