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 agentmods add skills/siddiqss/semantic-seo-suite/answer-engine-optimizernpx skills add siddiqss/semantic-seo-suite --skill answer-engine-optimizergit clone --depth 1 https://github.com/siddiqss/semantic-seo-suiteWrote 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/siddiqss/semantic-seo-suite/answer-engine-optimizer)<a href="https://agentmods.dev/skills/siddiqss/semantic-seo-suite/answer-engine-optimizer"><img src="https://agentmods.dev/badge/skills/siddiqss/semantic-seo-suite/answer-engine-optimizer.svg" alt="Measured on agentmods" 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 | $0.00147 | $0.01079 |
| Opus 5 | $0.00073 | $0.00540 |
| Sonnet 5 | $0.00029 | $0.00216 |
| Haiku 4.5 | $0.00015 | $0.00108 |
Grade A, and why
answer-engine-optimizer 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 5d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
answer-engine-optimizer
The citation feedback loop. Where seo-performance-tracker measures Google rankings,
this optimizes for being the source an LLM quotes — which, for a tool category whose
buyers research inside ChatGPT and Perplexity, is where a lot of the demand now decides.
It reuses the suite's spine: read the brand workspace, respect the grounding tier, tag every value, and feed results back into the map and calendar. It layers onto the on-page map — same nodes, hardened — it does not replace it.
Read first: ../../framework/answer-engine-optimization.md (the method + the honesty
rules), then ../../framework/macro-micro-semantics.md (the writing tactics it scores).
Preconditions
entity-profile.json+topical-map.jsonexist (run seo-brand-foundation / topical-map-builder first).- Drafts to score live in
brands/<slug>/drafts/. With no drafts yet, the skill still produces the hardening spec and the live-answer probe. - Live-answer probing needs
grounding.sources.web_search: true(T1). Without it, do the offline scoring only and say the probe was skipped — do not guess citations.
Workflow
-
Score citation-readiness (T0, offline). For each draft:
python ../../scripts/aeo_score.py --draft brands/<slug>/drafts/<slug>.md \ --schema-dir brands/<slug>/data/schema --jsonRun it after
validate_draft.pyis clean — AEO is advisory, fabrication is a gate. Collect score, grade, and the specific fixes (DEF / QA / TLDR / LIFT / BREV / SELF / SCHEMA). Scores aremeasured(mechanical), the recommended rewrites areasserted. -
Probe live answer engines (T1, web_search). For the highest-value target queries (core-section, especially comparison/alternative nodes), query them answer-style and record, per query + engine + date: is the brand named? cited with a link? which competitor sources are quoted instead? This is a dated spot check (n=1 per probe), labelled
measured— not a rank tracker. Never aggregate it into a visibility %.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 79 lines · 147 tokens per session scan A c369151bcd0a
answer-engine-optimizer is a skill published in the GitHub repository siddiqss/semantic-seo-suite (7 stars, last pushed 2mo ago), licensed MIT. It adds 147 tokens to every session and 1,079 once invoked, about $0.0007 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
fire-your-seo-agency
SEO·AEO·GEO·LLMO·NEO(네이버) 다섯 레인을 진단하고 직접 구현하는 스킬. 사이트를 검색엔진·답변엔진·생성 AI·네이버 AI 브리핑이 인용하는 1차 소스로 만든다. "SEO 해줘", "AI에 인용되게 해줘", "네이버 노출 늘려줘", "llms.txt 만들어줘" 류 요청에 사용. Use for "audit my site's SEO", "get my site cited by ChatGPT/Perplexity/AI Overviews", "improve search visibility", "create llms.txt", "answer engine /…
geo-loop
Run one bounded eGEOagents loop iteration over a workspace domain - read the charter and fresh collector data, do ONE unit of work, write substrate artifacts, append one Timeline entry and one LOG line. Use for loop mode, /geo:loop, scheduled GEO runs, or continuous monitoring.
content-scoring
Score content against the 10 GEO criteria with evidence and prioritized fixes. Use when users ask to score, rate, evaluate, or estimate ranking strength.
competitive-analysis
Analyze AI-search competitors for a query and recommend ranking strategy. Use when users ask competitor analysis, who ranks, or competitive landscape.
schema-generator
Generate JSON-LD schema markup for pages and content types with an implementation checklist. Use when users ask for schema, structured data, rich snippets, or markup.
validation-doctor
Check Brave Search and Chrome DevTools MCP availability and provide exact setup snippets. Use when validation dependencies are missing or uncertain.