Marketing Skills is an open-source library of reusable workflows that helps AI coding agents perform marketing and SEO tasks. It serves people working on search optimization, content, advertising, launches, analytics, and related marketing activities, and its catalogue entries are the individual skills agents can install.
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 kostja94/marketing-skills --skill localizationgit clone --depth 1 https://github.com/kostja94/marketing-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/kostja94/marketing-skills/localization)<a href="https://agentmods.dev/skills/kostja94/marketing-skills/localization"><img src="https://agentmods.dev/badge/skills/kostja94/marketing-skills/localization/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/kostja94/marketing-skills/localization"><img src="https://agentmods.dev/badge/skills/kostja94/marketing-skills/localization.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.00060 | $0.01699 |
| Opus 5.5 | $0.00024 | $0.00680 |
| Sonnet 5.5 | $0.00012 | $0.00340 |
| Haiku 4.5 | $0.00006 | $0.00170 |
Grade A, and why
localization-strategy 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 19d 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
2 near-identical copies found in the catalogue:
- localization-strategy — 100% identical, 199 lines differ
- localization-strategy — 100% identical, 199 lines differ
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Localization Strategy
Own the end-to-end localization decision and delivery lifecycle. Do not treat localization as a request to translate every source page or to create locale routes before the content is ready.
Boundaries
- This skill owns market and locale selection, scope, technical architecture, rollout, migration, release gates, and measurement.
- translation owns translated copy, terminology, style, review, and source-change updates.
- keyword-research owns target-market query research; do not translate a source keyword list.
- page-metadata, canonical-tag, and url-structure own their specialist implementation details. Coordinate them here without duplicating their full rules.
- Preserve project-specific product facts, route inventories, and terminology in the project context or implementation repository. Do not turn them into universal rules.
Establish the Current State
Read root contextus.md when present. Build the evidence set from the production site, route or CMS inventory, navigation and internal links, sitemap, source repository, analytics, and search data as available. A sitemap alone is not a complete page inventory.
Confirm:
- target markets, languages, and actual locale distinctions;
- current and proposed public URL patterns;
- default locale and whether it is prefixed;
- which page types are localized, source-only, or market-specific;
- content owner, glossary, review capacity, and update cadence;
- current route, canonical, hreflang, sitemap, language-switcher, and fallback behavior;
- existing indexed URLs that require redirects or compatibility handling.
When a site has thousands of same-template pages, inventory page types and representative examples rather than listing every URL.
Decide Whether a Locale Should Launch
Prioritize a locale using evidence such as existing demand, search opportunity, conversion or revenue potential, competitive depth, payment and support readiness, compliance, and the team's ability to keep content current.
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.
- 19d ago Changed · +5 lines · -21 tokens per session d4d3244e23f0
- 1mo ago Changed 30edc2904c08
- 1mo ago First seen · 142 lines · 81 tokens per session scan A 8973549520bf
localization-strategy is a skill published in the GitHub repository kostja94/marketing-skills (1,062 stars, last pushed 5d ago), licensed MIT. It adds 60 tokens to every session and 1,699 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-03.
Other skills, from other repositories
seo-hreflang
International SEO, multi-regional architecture, and hreflang tag validation. Enforces bidirectional return tags and cultural localization profiles.
SEO Content Optimizer
Analyzes and rewrites content to maximize search engine visibility without sounding robotic.
cold-outbound-sequencer
Use when the user asks to "build a B2B cold-outbound sequence", "design reply-triage branching", "plan a domain warmup / sending throttle", or "make my outbound CAN-SPAM / opt-in compliant"; produces a multi-step outbound sequence with reply-triage branches (positive / objection / referral / not-now / opt-out), a…
newsletter-monetization-planner
Use when the user asks to "monetize my newsletter", "build a sponsorship rate card", or "model paid-subscription revenue"; produces a revenue model (paid tiers, ad/sponsorship inventory + CPM/flat rate card, referral/boost loops), a list-growth ↔ revenue projection, and honest-offer / disclosure checks for the SEND-D…
contract-helper
Use when the user asks to "draft an influencer contract", "review these agreement terms", or "build a partnership template"; produces a full influencer agreement framework (scope, compensation, usage rights, exclusivity, FTC disclosure), a clause-by-clause review with red flags, and a negotiation cheat sheet. Not for…
sales-enablement-kit
Use when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch — battle cards vs each named alternative (where we win / where they win / trap questions, every fact traceable), a sales talk track derived…