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 sukirman1901/frontend-expert --skill fe-seogit clone --depth 1 https://github.com/sukirman1901/frontend-expertWrote 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/sukirman1901/frontend-expert/fe-seo)<a href="https://agentmods.dev/skills/sukirman1901/frontend-expert/fe-seo"><img src="https://agentmods.dev/badge/skills/sukirman1901/frontend-expert/fe-seo/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/sukirman1901/frontend-expert/fe-seo"><img src="https://agentmods.dev/badge/skills/sukirman1901/frontend-expert/fe-seo.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.00051 | $0.00560 |
| Opus 5 | $0.00026 | $0.00280 |
| Sonnet 5 | $0.00010 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
fe-seo 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.
What it actually says
FE SEO
Overview
Ship indexable, shareable pages. Don’t duplicate full LCP guides — pair with web-performance for CWV.
When to use
- Marketing/landing pages
- Public docs or content routes
- Adding meta/OG/Twitter cards
- SPA routes that should be crawlable
When to skip
- Authenticated-only app chrome with
noindex - Pure internal admin (still use semantic HTML + one h1)
MUST (public / shareable routes)
| Item | Rule |
|---|---|
| Title | Unique per route; aligns with visible H1 theme |
| Description | Meta description present and useful |
| H1 | One primary heading; sequential ladder (frontend-judgment) |
| OG | og:title, og:description, og:image (valid URL) on shareable pages |
| Indexability | SSR/SSG/prerender for marketing; avoid empty client-only shells |
Private app routes: prefer noindex rather than fake marketing meta.
Workflow
- Title + description — unique per route; match visible H1 theme
- Semantics — one H1; landmarks; meaningful link text
- OG/Twitter — image + title for share cards on public pages
- Indexability — SSR/SSG or prerender for public content
- CWV — defer to
web-performance/fe-devtoolsfor measured LCP/CLS - Canonical — set when duplicate URLs exist
Agent boundaries
- May decide: Metadata API vs static tags;
summaryvssummary_large_image - Must not: Same title on every route; keyword-stuffed invisible blocks; claim rankings without evidence
Checklist
- Unique
<title>/ metadata API equivalent - Meta description where public
- H1 + heading order sane (one h1)
- OG tags on shareable pages (image not 404)
- Public routes not blank without JS (when SEO matters)
-
noindexon private app chrome when appropriate
Depth
references/fe-seo.md. Perf: references/performance.md. Type: frontend-judgment Typography ladder.
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 · 65 lines · 51 tokens per session scan A 6d2894c71620
fe-seo is a skill published in the GitHub repository sukirman1901/frontend-expert (10 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 560 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…