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 matteotitta/genesys-skills --skill aeo-contentgit clone --depth 1 https://github.com/matteotitta/genesys-skillsWrote 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/matteotitta/genesys-skills/aeo-content)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/aeo-content"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/aeo-content/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/matteotitta/genesys-skills/aeo-content"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/aeo-content.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.00028 | $0.02827 |
| Opus 5 | $0.00014 | $0.01413 |
| Sonnet 5 | $0.00006 | $0.00565 |
| Haiku 4.5 | $0.00003 | $0.00283 |
Grade A, and why
aeo-content 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AEO Content
Produce articles citation-worthy by ChatGPT, Claude, Perplexity, and Google AI Overviews using the CITABLE framework + retrieval-citation-trust pipeline. Two output modes: CITABLE block (800-1,500 words) for definition/FAQ/short BOFU pages, and authority long-form (2,000-4,000 words) for competitor comparisons, listicles, how-to guides, and industry guides. Review gate is Level 3 because output publishes externally under client domain.
Doctrine inherited (Step 7 — 0626 rollout)
Output complies with:
output-tenets.md— the seven tenetsoutput-simplicity.md— length caps, three-layer source placement, robot-tells bandoc-output-structure.md— GDoc/Notion structural defaults (when published to either before site)- Step 6 calibration: see [[feedback_execution_doctrine_refinements_step6]]
Refinements applied to this skill:
| Code | Refinement | How it lands in aeo-content |
|---|---|---|
| R1 | Source placement (three layers) | Published articles are end-customer-facing. No "Sources" block on the rendered page — citations live in working draft for QA only, then convert to inline links inside the prose at publish-time. The page itself never carries a sources block; that's an AI-citation tell. |
| R3 | Product-update tone | Any product / feature mention frames as "[Product] does X" not "we are thrilled to announce [Product]." Even hero comparison pages stay even-keeled. |
| R6 | CTA hierarchy | TOFU/MOFU articles (definition, FAQ, how-to, industry guide) → blog-CTA + sign-up secondary. BOFU articles (competitor comparison, listicle ending in vendor pick) → sign-up or trial primary. |
| R7 | FAQ titles + no sources block | FAQ articles use canonical FAQ titles ("What is [X]?", "How does [X] work?", "How to [task]"). Never marketing-flavored variants ("X in 60 seconds," "The ultimate guide to X"). No sources block, two-types pattern (educational longer / how-to ≤4 bullets). |
| R8 | Entity-name headings | Section headings repeat the entity name — "What [Product] does," "How [Product] is different" — not pronoun headings ("What it does"). Customers scan for the entity. |
| R9 | Action-oriented section names | "How to set up [X]" beats "Setup." "Why [X] matters" beats "Importance." "How [X] compares to [Y]" beats "Comparison." |
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 · 154 lines · 124 tokens per session scan A 2823201df8f4
aeo-content is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 2,827 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
gingiris-go-global
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles.…
gr-competitor-research
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.