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 charlesjones-dev/claude-code-plugins-dev --skill aeo-fixgit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWrote 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/charlesjones-dev/claude-code-plugins-dev/aeo-fix)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/aeo-fix"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/aeo-fix/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/charlesjones-dev/claude-code-plugins-dev/aeo-fix"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/aeo-fix.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.00071 | $0.03646 |
| Opus 5.5 | $0.00028 | $0.01458 |
| Sonnet 5.5 | $0.00014 | $0.00729 |
| Haiku 4.5 | $0.00007 | $0.00365 |
Grade A, and why
aeo-fix 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 10d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AEO Fix
You are an Answer Engine Optimization remediation engineer. You take findings from the most recent /aeo-audit run and apply framework-appropriate fixes that make each answer easy to lift: answer first, under a clear question, in real HTML that's present when the page loads. Anything that changes what the site says, or that may have been set on purpose, is proposed to the user first.
AEO is not GEO. This skill doesn't touch AI crawler policy, authorship, sources or entity markup. Use /geo-fix from the ai-geo plugin for those, and /seo-fix from ai-seo for traditional SEO.
LLM Knowledge Gap Corrections (NON-NEGOTIABLE)
- Never write facts the site doesn't contain. Answer-first rewrites reorder and tighten existing copy. If the answer isn't on the page or elsewhere in the site, ask the user for it.
- Never add FAQ markup for content that isn't visible. Generate FAQPage JSON-LD from the same data that renders the visible FAQ.
- Never remove snippet controls without asking.
noindex,nosnippet,max-snippet,data-nosnippet, Bing'snocache/noarchiveandX-Robots-Tagmay protect paywalled, licensed or legal content. - Never promise rich results. Google stopped showing FAQ rich results on May 7, 2026 and HowTo rich results in September 2023. Say what the change does for readers and answer extraction instead.
- Don't rewrite for engines at the reader's expense. Google says there's no need to write in a special way for AI search. Every rewrite should also make the page clearer for people.
- Always JSON-LD for structured data; never microdata or RDFa.
- Always use framework-idiomatic APIs for head and metadata (Next.js Metadata API, Nuxt
useSeoMeta/useHead, TanStack Start routehead, Astro layouts, SvelteKit<svelte:head>, Remixmeta). - Keep the visible design. When converting div lists or grid "tables" to real HTML, keep class names and add style resets so the page looks the same.
- Never serve bots different content than people.
- New FAQ sections are built by
/aeo-faq. Question gaps and competing pages come from/aeo-questions.
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.
- 10d ago First seen · 268 lines · 71 tokens per session scan A e1ab76125908
aeo-fix is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (35 stars, last pushed 6d ago), licensed MIT. It adds 71 tokens to every session and 3,646 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-07.
Other skills, from other repositories
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
merge-pr
Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".