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 23blocks-OS/ai-maestro-plugins --skill agentic-seogit clone --depth 1 https://github.com/23blocks-OS/ai-maestro-pluginsWrote 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/23blocks-os/ai-maestro-plugins/agentic-seo)<a href="https://agentmods.dev/skills/23blocks-os/ai-maestro-plugins/agentic-seo"><img src="https://agentmods.dev/badge/skills/23blocks-os/ai-maestro-plugins/agentic-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/23blocks-os/ai-maestro-plugins/agentic-seo"><img src="https://agentmods.dev/badge/skills/23blocks-os/ai-maestro-plugins/agentic-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.00066 | $0.01439 |
| Opus 5.5 | $0.00026 | $0.00576 |
| Sonnet 5.5 | $0.00013 | $0.00288 |
| Haiku 4.5 | $0.00007 | $0.00144 |
Grade A, and why
agentic-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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic SEO
Repeatable workflow for auditing and implementing SEO on a web page. Standard SEO practice applies; the reference files hold the checks, templates and decisions specific to this skill.
First-Time Setup: Gather Site Configuration
Before running any sub-command for the first time in a session, ask the user for their website details if not already known. Store these as working context:
| Setting | Ask For | Example |
|---|---|---|
| Site Name | "What is your site/company name?" | Acme Corp |
| Domain | "What is your website domain?" | https://acme.com |
| X/Twitter Handle | "What is your X/Twitter handle?" (optional) | @acme_corp |
| Social Image Path | "Where are your social sharing images stored?" | /assets/social/ |
| Social Links | "Any social profile URLs?" (optional) | Twitter, GitHub, LinkedIn URLs |
| Framework | "What framework is your site built with?" | Angular, React, Next.js, etc. |
| Build Output Path | "Where does your built/prerendered HTML output to?" | dist/apps/web/browser/ |
| Sitemap Path | "Where is your sitemap.xml?" | public/sitemap.xml |
If the project has a CLAUDE.md with SEO patterns already defined, read it and extract these values automatically instead of asking.
Use these values as {SITE_NAME}, {DOMAIN}, {TWITTER_HANDLE}, {SOCIAL_IMAGE_PATH}, {BUILD_OUTPUT}, {SITEMAP_PATH} throughout all sub-commands.
When to use this skill
Trigger this skill when:
- A new page is created and needs SEO implementation
- An SEO audit is requested on an existing page
- Structured data (JSON-LD) needs to be added or updated
- llms.txt or llms-full.txt needs maintenance
- A quick checklist verification is needed before deploying
- A page is missing meta tags, OG tags, canonical URL, or sitemap entry
What Google says about AI search
Dated 2026-10-10: Google's guide "Optimizing your website for generative AI features on Google Search" (https://developers.google.com/search/docs/fundamentals/ai-optimization-guide, last updated 2026-07-10) says you don't need new machine readable files, AI text files, markup or Markdown to appear in Google Search; structured data isn't required for generative AI search and there is no special schema.org markup to add; Google Search doesn't use llms.txt, and having one neither harms nor helps visibility or rankings there; content does not need to be broken into tiny pieces. Standard SEO applies; re-check the guide before relying on this.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 90 lines · 66 tokens per session scan A 6fb4b0be46d5
agentic-seo is a skill published in the GitHub repository 23blocks-OS/ai-maestro-plugins (11 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,439 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-10-11.
Other skills, from other repositories
memory-search
Runs read-only SQL over the local EvoFlux session database (evoflux.db) for structured analysis that ordinary recall cannot answer, such as aggregating tool failures across sessions, filtering turns by role, agent, or time range, reconstructing a complete execution chain, or checking a remembered claim against what a…
Read, create and manipulate PDF files — extract text and tables, merge, split, rotate, reorder and delete pages, read and fill AcroForm fields, add or strip metadata, encrypt and decrypt, and generate new PDFs from HTML or from scratch. Also covers rasterising pages to images so a PDF can actually be looked at, and…
intelligent-ui
Helps agents choose prose, native controls, dashboards, motion, or 3D from the user's goal. Use when a user asks to explain, teach, compare, or present information visually, asks you to choose a format, requests a video or code-authored animation as the deliverable, or an interactive artifact may improve understanding…
diagram-design
Creates polished, accessible SVG diagrams as EvoFlux Work widgets or project files. Use when a user asks to design, draw, redraw, or polish a software architecture, data flow, API sequence, state machine, ER model, deployment, service journey, or process diagram, or asks to turn Mermaid, draw.io, or Excalidraw content…
agents
Guidance for AI coding agents working on the adeptability (adept) codebase. Humans: see README.md for usage and CONTRIBUTING.md for the contributor workflow.
authoring-adept-agents
Write a good, portable adept agent (subagent): trigger-shaped description, one job per agent, generator/evaluator separation, explicit boundaries, restricted tools. Apply when creating or editing an agent file or running adept agent add.