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 Infrasity-Labs/dev-gtm-claude-skills --skill blog-localizegit clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-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/infrasity-labs/dev-gtm-claude-skills/blog-localize)<a href="https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/blog-localize"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/blog-localize/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/infrasity-labs/dev-gtm-claude-skills/blog-localize"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/blog-localize.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.00169 | $0.01698 |
| Opus 5 | $0.00084 | $0.00849 |
| Sonnet 5 | $0.00034 | $0.00340 |
| Haiku 4.5 | $0.00017 | $0.00170 |
Grade A, and why
blog-localize 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 9d 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.
This is a copy
88% identical to blog-localize — 67 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog Localize, Cultural Deep-Adaptation
Takes a translated blog post and performs cultural adaptation so the result
feels like it was written for the target market, not translated into it.
This is the layer above blog-translate: it replaces examples, adjusts
tone, swaps references, and localizes the entire reading experience.
Key References
../blog-translate/references/cultural-adaptation.md, the shared cultural profiles file with substitution tables for DACH, Francophone, Hispanic, Japanese, and a custom template. Do not duplicate this file.
When to Use
- Right after
blog-translateproduces a base translation. - When existing translated content reads like "translated from English".
- When targeting a specific market, not just a language.
- When content needs local statistics, examples, and brand references.
Workflow
Phase 1: Locale Understanding
- Parse the locale code. Accept full codes (
de-DE,fr-CA,es-MX,pt-BR,zh-TW) or plain language codes (de,fr). - Load the cultural profile from
../blog-translate/references/cultural-adaptation.md.- If the locale has a profile, use it.
- If not, follow the "Custom-locale template" section in that reference to build a minimal profile inline.
- Read the translated post and identify adaptation targets.
Phase 2: Cultural Audit
Scan for elements that signal foreign origin:
| Element | What to look for |
|---|---|
| Brand examples | US or UK brands with no relevance locally |
| Statistics sources | US-only studies and surveys |
| CTAs | American-style aggressive calls-to-action |
| Idioms | Literally translated English expressions |
| Legal references | Foreign laws (CCPA, FTC) where local law applies (DSGVO, RGPD) |
| Cultural references | Foreign holidays, events, customs |
| Currency and pricing | USD without conversion or context |
| Tone | Too casual or too formal for the target market |
| Address form | Inconsistent Sie/du, tu/vous, formal/informal |
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.
- 9d ago First seen · 189 lines · 169 tokens per session scan A 14d02daf3536
blog-localize is a skill published in the GitHub repository Infrasity-Labs/dev-gtm-claude-skills (124 stars, last pushed 2mo ago), licensed MIT. It adds 169 tokens to every session and 1,698 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to blog-localize, differing in 67 lines, and is treated as a copy.
Other skills, from other repositories
hreflang-international
International / multilingual SEO audit focused on hreflang correctness. Detects and diagnoses the most common (and ranking-damaging) hreflang mistakes: missing or broken return tags, wrong language/region codes, missing x-default, self-referencing errors, conflicts between hreflang and canonical, and inconsistent…
geo-audit
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.
geo
GEO-first SEO analysis tool. Optimizes websites for AI-powered search engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) while maintaining traditional SEO foundations. Performs full GEO audits, citability scoring, AI crawler analysis, llms.txt generation, brand mention scanning, platform-specific…
geo-brand-mentions
Brand mention and authority scanner for AI visibility. Analyzes brand presence across platforms that AI models rely on for entity recognition and citation decisions. Produces a Brand Authority Score (0-100) with platform-specific recommendations.
geo-llmstxt
Analyzes and generates llms.txt files -- the emerging standard for helping AI systems understand website structure and content. Can validate existing llms.txt files or generate new ones from scratch by crawling the site.
agent-readiness-scan
Use when a client audit, GEO/AI-visibility snapshot, or remediation re-scan needs the Cloudflare agent-readiness score from isitagentready.com — e.g. Theo client audits, "is the site agent-ready", markdown negotiation / MCP / llms.txt / Content-Signal checks, or tracking score deltas after Tier 0/1 fixes.