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 eigent-ai/agent-skills --skill seo-auditgit clone --depth 1 https://github.com/eigent-ai/agent-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/eigent-ai/agent-skills/seo-audit)<a href="https://agentmods.dev/skills/eigent-ai/agent-skills/seo-audit"><img src="https://agentmods.dev/badge/skills/eigent-ai/agent-skills/seo-audit/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/eigent-ai/agent-skills/seo-audit"><img src="https://agentmods.dev/badge/skills/eigent-ai/agent-skills/seo-audit.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.00069 | $0.00490 |
| Opus 5.5 | $0.00028 | $0.00196 |
| Sonnet 5.5 | $0.00014 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
seo-audit 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 1mo 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Audit
Overview
Use this skill to evaluate how well a page or site can be discovered, understood, and cited by search engines and AI answer engines. Focus on prioritized fixes that connect directly to ranking, crawlability, conversion intent, or answer eligibility.
Workflow
- Identify the target page, keyword or query set, business goal, and audience.
- Inspect the available page content, rendered HTML, metadata, and site structure.
- Audit core on-page SEO:
- Title, meta description, H1/H2 structure, URL, canonical, alt text, schema, and internal links.
- Keyword intent alignment, content depth, duplication, and missing sections.
- Audit technical risk where access permits:
- Indexability, robots directives, performance signals, mobile rendering, broken links, redirects, and structured data validity.
- For AI-search optimization, check whether the page provides concise answerable claims, clear entity relationships, sourceable facts, comparison language, and trustworthy proof.
- Compare competitors when supplied and identify missing topics, formats, keywords, and proof points.
- Deliver a prioritized fix list with expected impact, effort, and concrete edits.
Output Pattern
Use this structure unless the user requests another format:
- Summary of the strongest opportunities.
- Critical fixes.
- On-page recommendations.
- Technical recommendations.
- AI-search recommendations.
- Content gap opportunities.
- Suggested title, meta description, headings, and internal links when useful.
Example Prompts
Run an SEO audit on this landing page [paste content]. Check keyword density, heading structure, meta description, and internal linking. Give me a prioritized fix list.Run /ai-seo on our homepage. We want to rank in AI-generated answers for "best project management tool for remote teams". What needs to change?Compare our blog content against these 3 competitor URLs. What topics are they ranking for that we're missing? Give me a content gap report.
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.
- 1mo ago First seen · 42 lines · 69 tokens per session scan A ac2afc38943c
seo-audit is a skill published in the GitHub repository eigent-ai/agent-skills (24 stars, last pushed 12d ago), licensed Apache-2.0. It adds 69 tokens to every session and 490 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.