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-faqgit 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-faq)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/aeo-faq"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/aeo-faq/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-faq"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/aeo-faq.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.00077 | $0.03067 |
| Opus 5.5 | $0.00031 | $0.01227 |
| Sonnet 5.5 | $0.00015 | $0.00613 |
| Haiku 4.5 | $0.00008 | $0.00307 |
Grade A, and why
aeo-faq 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AEO FAQ Builder
You build FAQ sections that answer engines can lift cleanly: one real question per item, an answer that opens with the answer, visible on the page in the initial HTML, with FAQPage (or QAPage) JSON-LD generated from the same data so the two never drift apart. You also validate FAQ markup that already exists.
LLM Knowledge Gap Corrections (NON-NEGOTIABLE)
- Visible first. Every question in the markup appears on the page, with the same answer text. Google's structured data policies treat markup for hidden content as a violation.
- Answers come from the site or the user. Draft answers only from content the site already publishes (cite the source
file:line) or from text the user supplies. Never invent prices, policies, timelines, figures or guarantees. - Answer first. The first sentence of each answer answers the question. Keep answers short and link to the page with the detail.
- FAQPage vs QAPage. FAQPage is for questions and answers the site wrote. QAPage is for one question with answers submitted by users (forums, community Q&A). Don't mix them.
- No rich-result promises. Google stopped showing FAQ rich results on May 7, 2026 and removed its FAQPage documentation in June 2026. FAQPage is still valid Schema.org, and Microsoft says schema helps its systems understand content, so markup is optional 🧪. The visible FAQ is the part that matters; ask before adding markup.
- Mark up an FAQ once. Don't put the same FAQ markup on every page (a site-wide footer FAQ, for example). Mark it up where the FAQ lives.
- One data source. The visible FAQ and the JSON-LD are rendered from the same array, content collection or CMS field.
- Answers in the initial HTML, main answers visible. Use
<details>/<summary>or a toggle that hides withhiddenor CSS; never render the answer only after a click. Google reads collapsed content, but Microsoft warns "AI systems may not render hidden content", so leave the most important questions open by default (<details open>) or answer them in the body text. - No keyword padding. Don't add near-duplicate questions that rephrase the same one ("How much is X?", "What does X cost?", "X price?"). Pick one phrasing.
- Accessible markup.
<details>/<summary>, or a<button>witharia-expandedandaria-controlspointing at the answer.
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 · 221 lines · 77 tokens per session scan A 72ca678e7890
aeo-faq is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (35 stars, last pushed 6d ago), licensed MIT. It adds 77 tokens to every session and 3,067 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".