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 charlacsina/openaeo-audit --skill aeo-fix-passgit clone --depth 1 https://github.com/charlacsina/openaeo-auditWrote 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/charlacsina/openaeo-audit/aeo-fix-pass)<a href="https://agentmods.dev/skills/charlacsina/openaeo-audit/aeo-fix-pass"><img src="https://agentmods.dev/badge/skills/charlacsina/openaeo-audit/aeo-fix-pass/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/charlacsina/openaeo-audit/aeo-fix-pass"><img src="https://agentmods.dev/badge/skills/charlacsina/openaeo-audit/aeo-fix-pass.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.00087 | $0.00730 |
| Opus 5 | $0.00044 | $0.00365 |
| Sonnet 5 | $0.00017 | $0.00146 |
| Haiku 4.5 | $0.00009 | $0.00073 |
Grade A, and why
aeo-fix-pass 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 11d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AEO fix pass
Make a site readable, trustworthy and quotable by AI answer engines, then prove the score moved.
Requires the OpenAEO MCP server (aeo_audit, aeo_fix_files, aeo_fix_html, aeo_check_html).
If those tools aren't available, tell the user to add it:
{ "mcpServers": { "openaeo": { "command": "npx", "args": ["-y", "openaeo-audit", "mcp"] } } }
Steps
-
Audit. Call
aeo_auditon the user's domain. Report the score, band and failing checks in plain language. Lead with the retrieval gates — a failing gate caps everything else, so there's no point tuning schema if AI bots get a 403 or the content only renders after JS. -
Find where things live. Locate the site's public/static root (
public/,static/,dist/, or the repo root) and the template that owns<head>. Don't guess — check. -
Generate the files. Call
aeo_fix_files. Writerobots.txtandllms.txtto the static root. If arobots.txtalready exists, merge rather than overwrite — preserve their existing rules and add the AI-crawler allows. -
Fix the pages. For each key page (home, pricing, about, FAQ), read the HTML, call
aeo_fix_html, and writefixedHtmlback. For templated sites, apply the equivalent change to the layout/template instead of every rendered page. -
Verify. Call
aeo_check_htmlon what you wrote. After the user deploys, re-runaeo_auditto confirm the score actually moved.
Rules
- Never invent facts. Generated files contain
[bracketed]placeholders — prices, counts, founding years, addresses, social URLs. Ask the user for real values or leave the brackets. A fabricated number in schema is worse than no schema: assistants cross-check, and unverifiable claims cost trust. - Schema must mirror what's visible. Don't put a rating or price in JSON-LD that doesn't appear on the page.
- Additive only.
aeo_fix_htmladds missing<head>elements; it never rewrites content. Any copy changes are a suggestion for the user to approve, not something you apply silently. - Show your work. List the files you're about to create or modify, and let the user confirm before writing.
- Don't hide anything from users. Never add text that's visible to crawlers but not to
people (hidden divs,
display:nonekeyword blocks, instructions aimed at AI readers). It's cloaking, assistants penalise it, and it will destroy the trust the rest of this work builds.
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.
- 11d ago First seen · 52 lines · 87 tokens per session scan A ae6c9445c1f9
aeo-fix-pass is a skill published in the GitHub repository charlacsina/openaeo-audit (0 stars, last pushed 27d ago), licensed MIT. It adds 87 tokens to every session and 730 once invoked, about $0.0004 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…