NotFair Plugin is a collection of open-source SEO, generative-engine-optimization, and marketing workflows that AI agents can follow. It helps agents audit websites, analyze search and advertising data, plan campaigns, and make reviewable marketing changes; the catalogue entries are its skills, instructions, MCP connection, and plugin.
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 nowork-studio/notfair-plugin --skill hreflang-internationalgit clone --depth 1 https://github.com/nowork-studio/notfair-pluginWrote 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/nowork-studio/notfair-plugin/hreflang-international)<a href="https://agentmods.dev/skills/nowork-studio/notfair-plugin/hreflang-international"><img src="https://agentmods.dev/badge/skills/nowork-studio/notfair-plugin/hreflang-international/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/nowork-studio/notfair-plugin/hreflang-international"><img src="https://agentmods.dev/badge/skills/nowork-studio/notfair-plugin/hreflang-international.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.00242 | $0.01399 |
| Opus 5 | $0.00121 | $0.00700 |
| Sonnet 5 | $0.00048 | $0.00280 |
| Haiku 4.5 | $0.00024 | $0.00140 |
Grade A, and why
hreflang-international 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
International & Hreflang SEO Audit
You are a senior international-SEO engineer. Your job is to verify that a multilingual / multi-region site sends Google clean, consistent language and region signals — and to pinpoint exactly which hreflang errors are causing the wrong page to surface for the wrong audience.
Hreflang is unforgiving: a single broken return tag silently drops the whole cluster's hreflang benefit. This skill is mechanical and precise.
Credit: capability inspired by the open-source
claude-seoproject (MIT, Agrici Daniel). Implementation is original to NotFair.
Step 0 — Scope
Collect:
- Site URL (
$SITE_URL). - Language/region versions that exist (e.g.
th,en,en-US,th-TH). Infer from the site if the user doesn't list them. - How versions are served — subdirectory (
/en/), subdomain (en.), ccTLD (.co.th), or URL parameter.
Pick a small set of representative URL clusters (the same page in each language, e.g. homepage + one product page) to inspect in depth. Hreflang errors repeat across templates, so 2–3 clusters reveal systemic problems.
Phase 0 — Preflight & data
Read and follow ../shared/preamble.md for script discovery and GSC auth.
If GSC is connected, check the Performance → search results report filtered by country to see whether the wrong language version ranks in a given market — that confirms a live hreflang/targeting problem, not just a theoretical one.
Phase 1 — Discover the hreflang signals
For each representative URL, find hreflang annotations in all three possible locations and record where they live:
- HTML
<head>—<link rel="alternate" hreflang="..." href="..." /> - HTTP headers —
Link:header (common for PDFs / non-HTML). - XML sitemap —
<xhtml:link rel="alternate" hreflang="...">entries.
A site should use one method consistently. Using two that disagree is a common bug — flag it.
Phase 2 — Validate every annotation
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 · 130 lines · 242 tokens per session scan A 8364f78eb44f
hreflang-international is a skill published in the GitHub repository nowork-studio/notfair-plugin (3,703 stars, last pushed yesterday), licensed MIT. It adds 242 tokens to every session and 1,399 once invoked, about $0.0012 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-30.
Other skills, from other repositories
react-i18n
Use when implementing translations in a React app (not Next.js) with react-i18next — useTranslation, namespaces, pluralization, Suspense.
laravel-i18n
Use when implementing Laravel translations — (), transchoice(), lang files, pluralization, locale middleware, or formatting.
blog-multilingual
One-command multilingual blog creation. Writes a blog post, translates it into user-specified languages, applies cultural adaptation, and emits hreflang tags, sitemap entries, and a CMS-ready language map. The complete write-to-publish pipeline for international content. Orchestrates blog-write, blog-translate…
blog-translate
Translate existing blog posts into one or more target languages with SEO-optimized localization. Produces native-quality translations that preserve markdown structure, frontmatter, schema JSON-LD, image and chart embeds, and citation capsules. Localizes keywords, meta tags, numbers, dates, currencies, and quote styles…
nextjs-i18n
Use when implementing i18n in Next.js 16 — next-intl or DIY dictionaries, locale routing, language switch, or formatters.
astro-i18n
Use when implementing i18n in Astro — locale routing strategies, getRelativeLocaleUrl/getAbsoluteLocaleUrl, Astro.currentLocale, or hreflang with sitemap.