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 indranilbanerjee/neels-plugins --skill aeo-auditgit clone --depth 1 https://github.com/indranilbanerjee/neels-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/indranilbanerjee/neels-plugins/aeo-audit)<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/aeo-audit"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/aeo-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/indranilbanerjee/neels-plugins/aeo-audit"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/aeo-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.00029 | $0.02283 |
| Opus 5.5 | $0.00012 | $0.00913 |
| Sonnet 5.5 | $0.00006 | $0.00457 |
| Haiku 4.5 | $0.00003 | $0.00228 |
Grade A, and why
aeo-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 2d 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.
This is a copy
95% identical to aeo-audit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:aeo-audit
Purpose
Evaluate the brand's visibility and accuracy across AI answer engines. Analyze how the brand is cited, described, and recommended by ChatGPT, Perplexity, Google AI Mode (the conversational search surface that became Google's default at I/O 2026 — ~1B MAUs as of May 2026), Google AI Overviews, Gemini, and Microsoft Copilot. Produce optimization recommendations to improve AI visibility.
AI Mode vs AI Overviews — why both matter: AI Overviews are the summary block at the top of a classic Google SERP and trigger on a subset of queries. AI Mode is a conversational tab (and now the default search experience for opted-in users) backed by Gemini 3.5 Flash with deeper reasoning, follow-ups, and a different citation pattern. The two surfaces select different sources for the same query in a large share of cases (internal observation, 05/2026 — "40–60%" is a rough estimate; re-verify against your own probe set). Audit both.
Cross-reference with GSC AI Performance Report (rolled out 3 June 2026): The Google Search Console AI Performance Report (UK rollout first, global to follow) gives you actual impressions in AI Overviews + AI Mode for verified properties. Synthetic probe results from this skill should be reconciled against GSC actuals — see /digital-marketing-pro:gsc-ai-performance for the workflow. Important caveat: the GSC report intentionally excludes click data; click-through attribution must come from GA4 (the new AI Assistant channel group, added 13 May 2026, captures Medium=ai-assistant referrals from ChatGPT/Gemini/Claude; see /digital-marketing-pro:analytics-insights).
Google's official position on AI optimization (Google AI Optimization Guide, updated 15 May 2026): no llms.txt, no AI-specific schema, no separate AI eligibility gate. Pages eligible for snippets in classic Search are eligible for AI Features. Don't manufacture work around fictional ranking factors — /digital-marketing-pro:aeo-geo documents what does work (entity consistency, citation-worthy snippets, knowledge graph alignment).
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.
- 2d ago First seen · 115 lines · 29 tokens per session scan A 60a7fa3d3a95
aeo-audit is a skill published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 2,283 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to aeo-audit, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
continuous-improvement-loop
Run the Part 12 continuous improvement loop into a quarterly brief for leadership. "produce the quarterly improvement brief".
competitor-pages
Build competitor comparison pages: X-vs-Y, alternatives and roundups, with schema. "create a vs page".
yearly-planner
Produce the Part 8 yearly planner: quarterly themes and monthly initiatives. "plan the whole year month by month".
attribution-report
Run attribution on real conversion paths, comparing models. "which channels actually drive revenue".
validate-output
Validate content structure against a schema: sections, word counts. "scan for leftover placeholders".
add-integration
Add a custom MCP integration: scaffold the server, write .mcp.json, test it. "add a new MCP server".