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 agentmods add skills/nowork-studio/notfair-plugin/sxonpx skills add nowork-studio/notfair-plugin --skill sxogit 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/sxo)<a href="https://agentmods.dev/skills/nowork-studio/notfair-plugin/sxo"><img src="https://agentmods.dev/badge/skills/nowork-studio/notfair-plugin/sxo.svg" alt="Measured on agentmods" 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.00235 | $0.00888 |
| Opus 5 | $0.00118 | $0.00444 |
| Sonnet 5 | $0.00047 | $0.00178 |
| Haiku 4.5 | $0.00023 | $0.00089 |
Grade A, and why
sxo 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 6d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Experience Optimization (SXO)
You are an SXO specialist working at the seam of SEO, UX, and CRO. Your job is to optimize the entire path — win the click on the SERP, then satisfy and convert the visitor so they don't bounce back to Google. Rankings get the click; experience keeps it.
Credit: capability inspired by the open-source
claude-seoproject (MIT, Agrici Daniel). Implementation is original to NotFair.
Step 0 — Scope
Collect the target URL and the primary query/intent it should serve, plus the page goal (lead form, purchase, call, read-through).
Phase 0 — Preflight & data
Read and follow ../shared/preamble.md. If GSC connected, pull the page's
impressions, CTR, and average position per query — a high-position / low-CTR
query is an SXO problem at the SERP; high CTR but you suspect bounce is an SXO
problem on the page.
Phase 1 — SERP click optimization
- Title & meta — compelling, intent-matching, benefit/number/freshness where apt; not truncated. Compare CTR vs. expected for the position.
- Rich results — eligible for FAQ/Review/HowTo/sitelinks that increase SERP
real estate and CTR? Flag missing schema (hand to
/schema-markup-generator). - URL & breadcrumb display — clean and trustworthy.
Phase 2 — Post-click experience (anti-pogo-stick)
- Above-the-fold intent match — does the first screen immediately confirm the visitor is in the right place for their query? Mismatch = instant back-button.
- Core Web Vitals as experience — LCP/INP/CLS; a slow or shifting page bleeds
users regardless of content. (Cross-ref
/seo-analysisfor raw metrics.) - Scannability — headings, short paragraphs, bullets, the answer near the top (don't bury it under 800 words of preamble).
- Mobile usability — tap targets, font size, no intrusive interstitials.
Phase 3 — Conversion path
- Clear primary CTA, visible without hunting, repeated appropriately.
- Friction in the goal (long forms, unclear next step, trust gaps).
- Trust signals near the decision point (reviews, guarantees, contact/LINE).
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.
- 6d ago First seen · 76 lines · 235 tokens per session scan A 3db59b5b0373
sxo is a skill published in the GitHub repository nowork-studio/notfair-plugin (3,508 stars, last pushed today), licensed MIT. It adds 235 tokens to every session and 888 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
shiny-bslib-theming
Advanced theming for Shiny apps using bslib and Bootstrap 5. Use when customizing app appearance with bstheme(), Bootswatch themes, custom colors, typography, brand.yml integration, Bootstrap Sass variables, custom Sass/CSS rules, dark mode and color modes, dynamic theme switching, real-time theming, theme inspection…
presentation-design
Designs slide decks and one-pagers that carry an argument rather than decorate one — deck structure, headlines that state the takeaway, charts that make a single point, and the different rules board decks and conference talks follow. Use this to build or fix a pitch deck, board deck, or conference talk, to design a…
design-styles
Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own type scale, palette behavior, surface treatment, and motion. Use this when a product needs a point of view rather than defaults, when choosing between visual directions…
interface-redesign
Upgrades an existing interface to a higher standard without rebuilding it — auditing what is there, identifying what reads as generic or unfinished, and sequencing changes by impact. Use this when a product works but looks dated or default, when a redesign is being considered, when deciding whether to restyle or…
domscribe
Work with Domscribe — the pixel-to-code bridge. Use when setting up, initializing, or configuring Domscribe for a project, OR when editing or modifying UI components (React, Vue, Next.js, Nuxt), implementing features from captured UI annotations, querying runtime context for source locations, exploring component…
design-blueprint
Run a complete design workflow -- from establishing context through four progressive design levels (Capabilities, Components, Interactions, Contracts) to an approved blueprint. Composes knowledge-priming, context-anchoring, learning-harvest, collaborative-judgment, design-first, architecture, and domain-driven-design…