cf-aeo-check

cf-aeo-check is a skill for Claude Code from indranilbanerjee/contentforge. It costs 187 tokens per session (2,253 once invoked), scanned A, original, MIT.

A post-publication check for whether a web article appears in Google search’s AI-generated summaries and whether its page contains information those systems can read. It also keeps a history of checks for each brand.

In plain words
What is it for?
Checking target search queries, reviewing a published URL, recording citation and ranking changes, and identifying content that may need updating.
Why use it?
It shows whether an article actually earns search citations after publication, instead of relying only on predictions made before writing. It can reveal missing definitions, dates, structured data, or tables that make the page harder to use.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

Part of the contentforge plugin — 22 skills, 9 commands, 13 agents shipped together

Good fit Checking target search queries, reviewing a published URL, recording citation and ranking changes, and identifying content that may need updating.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/indranilbanerjee/contentforge/cf-aeo-check
Install

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.

Any agent
npx skills add indranilbanerjee/contentforge --skill cf-aeo-check
Clone the repo
git clone --depth 1 https://github.com/indranilbanerjee/contentforge

Made for: Claude Code.

Or install contentforge, the plugin that ships this one along with the rest of its 22 skills, 9 commands, 13 agents.

Wrote 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.

agentmods badge for cf-aeo-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/indranilbanerjee/contentforge/cf-aeo-check/github.svg)](https://agentmods.dev/skills/indranilbanerjee/contentforge/cf-aeo-check)
Your own site
<a href="https://agentmods.dev/skills/indranilbanerjee/contentforge/cf-aeo-check"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/contentforge/cf-aeo-check/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.

agentmods 80×15 button for cf-aeo-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/indranilbanerjee/contentforge/cf-aeo-check"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/contentforge/cf-aeo-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 187 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,253 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00187 $0.02253
Opus 5 $0.00093 $0.01126
Sonnet 5 $0.00037 $0.00451
Haiku 4.5 $0.00019 $0.00225

Measured 9d ago against content hash ae2540caf58d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

cf-aeo-check 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/cf-aeo-check/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AEO Citation Check — Post-Publication

Close the loop that /contentforge:cf-brief opens. The brief checks AI Overview presence and citation patterns before production; this skill verifies — after publication — whether the piece actually earned citations, tracks the trend across re-checks, and routes losses to /contentforge:content-refresh with specific evidence.

Honest scope — read before promising anything

  • What this skill measures directly: Google SERP state for the target queries via web search (AI Overview present? which domains are cited/visible? does the piece rank?), and on-page extractability of the published URL via web fetch (definition block intact, dates visible, schema present, metrics tables surviving the CMS).
  • What it cannot measure directly: citations inside ChatGPT, Perplexity, Gemini or Copilot answers — there is no public API for "was I cited," and probing chat UIs is not reproducible. Cross-engine measurement needs a third-party tracker (Profound, Otterly, Conductor AgentStack, HubSpot AEO — same list the Phase 6 optimizer names). If such a connector is available in the tool list, use it and label the data's source; if not, say plainly that engine coverage is Google-observable-only. Never present an estimate as a measurement.

When to Use

Use /contentforge:cf-aeo-check when:

  • A piece published 2+ weeks ago and you want to know if AI engines are citing it (earlier checks mostly measure indexing lag, not merit)
  • You're deciding which content to refresh and want citation evidence, not hunches
  • A competitor appears in AI Overviews for your target query and you want the delta documented
  • You want a standing citation scoreboard per brand across re-checks

Not for: pre-production research (that's /contentforge:cf-brief), rank tracking as a discipline (this is a citation check, not a rank tracker), or measuring engines it cannot observe (see Honest scope).

Required Inputs

Minimum required (one of):

  • Published URL — the live page to check
  • Requirement ID (e.g., REQ-001) — resolved via the brand's tracking backend to the published URL recorded at completion; fails with a clear message if no URL was recorded

Read the full file on GitHub · 125 lines

Changes

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.

  1. 9d ago First seen · 125 lines · 187 tokens per session scan A ae2540caf58d

Subscribe to this mod's changes

cf-aeo-check is a skill published in the GitHub repository indranilbanerjee/contentforge (26 stars, last pushed 22d ago), licensed MIT. It adds 187 tokens to every session and 2,253 once invoked, about $0.0009 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-30.

Related

Other skills, from other repositories

continuous-improvement-loop

Run Part 12 of the engagement methodology — the continuous improvement loop that aggregates quarterly-review, customer-feedback, competitive, and operating signals into a Quarterly Product & Offering Improvement Brief for business leadership, plus fast 1-3 page ad-hoc briefs when a significant signal lands…

indranilbanerjee/digital-marketing-pro · 148 tokens

four-core-documents

Produce Part 3 of the 12-Part engagement: the four strategic-spine documents across 61 steps — 3.1 Business & SBU Analysis, 3.2 Segmentation Framework, 3.3 Brand Positioning & Communications, 3.4 DMFlow — with --doc single-document runs, --view v2 re-runs, and a --combined executive stitch. Triggers on…

indranilbanerjee/digital-marketing-pro · 164 tokens

seo-plan

Build a 12-month SEO strategy and phased roadmap with industry templates (SaaS, ecommerce, local, publisher, agency). With fresh specialist outputs it runs as a dispatcher: scores four pillars — technical, content, topical, AI search — and makes the weakest pillar the plan's lead theme; missing specialists re-run only…

indranilbanerjee/digital-marketing-pro · 177 tokens

aeo-audit

Audit how a brand appears across the 6 canonical AI answer surfaces — ChatGPT, Perplexity, Google AI Mode, AI Overviews, Gemini, Copilot — probing 10-25 queries into a numbered output bundle with per-platform visibility scorecards, citation-accuracy checks, a competitor matrix, content gaps, and an optimization…

indranilbanerjee/digital-marketing-pro · 173 tokens

c2pa-metadata

Embed a C2PA provenance manifest into an AI-generated marketing asset (PNG, JPG, WebP, GIF, TIFF, MP4, MOV, WebM, MP3, WAV, PDF) via scripts/embed-c2pa.py — produces a signed copy of the file carrying IPTC digital-source-type AI claims, an optional c2pa.ai-disclosure assertion for EU AI Act Article 50 (applicable 2…

indranilbanerjee/digital-marketing-pro · 183 tokens

growth-plan

Produce the 11-section Growth Plan — the flagship Part 8 client-facing deliverable that synthesises Parts 1-7 of the engagement into a single 20-30 page executable strategy with three-scenario forecasts, an In-Market/Out-Market budget split, and a 30/60/90 timeline, exported to PDF and DOCX. Triggers on…

indranilbanerjee/digital-marketing-pro · 161 tokens