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/tmj-90/gaffer/aeonpx skills add tmj-90/gaffer --skill aeogit clone --depth 1 https://github.com/tmj-90/gafferWrote 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/tmj-90/gaffer/aeo)<a href="https://agentmods.dev/skills/tmj-90/gaffer/aeo"><img src="https://agentmods.dev/badge/skills/tmj-90/gaffer/aeo.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.00105 | $0.01024 |
| Opus 5 | $0.00053 | $0.00512 |
| Sonnet 5 | $0.00021 | $0.00205 |
| Haiku 4.5 | $0.00011 | $0.00102 |
Grade A, and why
aeo 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 4d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimise content for LLM citation
AEO (Answer Engine Optimisation) optimises content to be cited in LLM-generated responses — distinct from SEO, which optimises for click-through rankings. The signal sets differ.
AEO vs SEO
| SEO | AEO | |
|---|---|---|
| Optimises for | Click-through ranking | Citation as authoritative source |
| Success metric | Position 1-10, organic traffic | Citation count across LLMs |
| Key signals | Backlinks, keywords, page speed | E-E-A-T, structured facts, primary-source signals |
| Update cadence | Weeks–months | Days–weeks (LLM training cycles) |
Both coexist — a page can rank #1 on Google AND be cited by Perplexity.
E-E-A-T signals for LLM citation
LLMs prefer content that looks like a primary source to their training data:
| Signal | Implementation |
|---|---|
| Experience | First-person case studies; dated real examples ("In our 2026 audit of 50 repos…") |
| Expertise | Author bio with credentials; technical depth; cite primary sources |
| Authoritativeness | External backlinks from authority domains; schema.org markup; Wikipedia presence |
| Trustworthiness | HTTPS; contact info; transparent corrections; verifiable claims with data |
Factual density — LLMs prefer pages with a high ratio of verifiable claims per 1,000 words. Prose that states facts > prose that describes opinions.
Content structure for citation
LLMs extract from:
- Direct-answer paragraphs — a question as a heading followed immediately by a 1–2 sentence direct answer.
- Structured data — FAQPage and HowTo schema (see
schema-markup). - Definition blocks — "X is [concise definition]" sentences at the start of sections.
- Comparison tables — LLMs reproduce tables well; use for vs. comparisons and feature matrices.
Citation-hostile patterns to avoid
- Gated content (LLMs can't read it during training crawls).
- JavaScript-rendered text (crawlers often miss it).
- Opinion without evidence ("we believe X is important").
- Content updated without a
dateModifiedschema field. - No author or institutional attribution.
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.
- 4d ago First seen · 75 lines · 105 tokens per session scan A 14b875584f59
aeo is a skill published in the GitHub repository tmj-90/gaffer (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 105 tokens to every session and 1,024 once invoked, about $0.0005 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
mobile-developer
Expert knowledge in mobile app development for iOS, Android, and cross-platform solutions.
skill-creator
Create or update AnkaLoop skills. Use when designing, structuring, or packaging skills with scripts, references, and assets. This skill should be used when users want to create a new skill (or update an existing skill) that extends AnkaLoop's capabilities with specialized knowledge, workflows, or tool integrations.
ai-engineer
Expert knowledge in AI/ML development, model deployment, and MLOps practices.
gh-ci-analyzer
使用 gh CLI 分析 GitHub Actions CI 日志，提供结构化的故障诊断和报告.
security-best-practices
Security best practices and vulnerability prevention guidelines.
react-developer
Expert knowledge in React development, hooks, state management, and modern React patterns.