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 maxschottke-spec/seo-survival-kit --skill ai-citations-trackergit clone --depth 1 https://github.com/maxschottke-spec/seo-survival-kitWrote 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/maxschottke-spec/seo-survival-kit/ai-citations-tracker)<a href="https://agentmods.dev/skills/maxschottke-spec/seo-survival-kit/ai-citations-tracker"><img src="https://agentmods.dev/badge/skills/maxschottke-spec/seo-survival-kit/ai-citations-tracker/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/maxschottke-spec/seo-survival-kit/ai-citations-tracker"><img src="https://agentmods.dev/badge/skills/maxschottke-spec/seo-survival-kit/ai-citations-tracker.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.00148 | $0.02841 |
| Opus 5 | $0.00074 | $0.01421 |
| Sonnet 5 | $0.00030 | $0.00568 |
| Haiku 4.5 | $0.00015 | $0.00284 |
Grade A, and why
ai-citations-tracker scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: [Read, Write, Bash(node:*), Bash(curl:*), Bash(launchctl:*), Bash(crontab:*)] How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Citations Tracker
Overview
Most "AI search visibility" advice is descriptive ("you should rank in AI Overviews"). This skill is the measurement loop: a weekly cron job that asks the same brand-mention prompts to AI surfaces, parses the answers for your brand vs competitors, and logs results to NDJSON for trend analysis.
This is the possible-early-signal companion to [[post-core-update-recovery]]:
- Classical Sistrix VI / GSC clicks lag Google by 3-5 days
- Hypothesis (N=1, currently unproven): AI citation counts MAY start moving 2-6 weeks before classical SERP recovery shows up. In the pilot case this pattern suffered a setback — the AI-citation rise coincided with a pre-update plateau that a subsequent Core Update erased (see
post-core-update-recovery/LESSONS.md, 2026-06-03 correction). Log the signal; do not report recovery based on it alone. - If your AI citations are climbing while VI is flat, that is worth logging — not confirmation that recovery is on track. If both are flat, the authority signals from [[ai-search-rescue]] Tactic 4 (Author + Person-Schema) need more time or aren't reaching the model retrieval layer.
When to use
- A site running active Core-Update recovery — track AI citations as the leading recovery indicator
- A brand wanting to know whether ChatGPT / Perplexity / AI Overviews actually mention them (most brands don't measure this — they guess)
- An agency reporting to clients on "AI search visibility" — needs hard numbers, not vibes
- A YMYL / B2B vendor whose buyers research via ChatGPT before contact sales — citation frequency is a direct lead-gen signal
Don't use for:
- One-off citation snapshots (use the manual workflow in [[ai-search-rescue]] instead — no cron needed)
- Pure SERP ranking tracking (use [[seo-outreach-report]] + [[competitor-deep-audit]])
- Optimizing the content itself (that's [[ai-search-rescue]] — this skill measures, that skill optimizes)
Architecture
ai-citations-config.json (your prompts + competitors + API keys via env)
↓
ai-citations-fetch.example.js (run weekly via cron)
↓
ai-citations-history.ndjson (append-only, per-week records)
↓
your trend chart / Sistrix-style overlay
What ships with it
2 files 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.
- 10d ago First seen · 179 lines · 148 tokens per session scan A d6a8578e522c
ai-citations-tracker is a skill published in the GitHub repository maxschottke-spec/seo-survival-kit (9 stars, last pushed 1mo ago), licensed MIT. It adds 148 tokens to every session and 2,841 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
content-seo
When the user wants to brief, write, review, optimize, or publish public SEO content. Also use for article outlines, blog posts, landing-page copy, refreshes, and ranking-oriented editorial drafts.
backlink-analysis
When the user wants backlink, referring-domain, anchor, link-quality, link-gap, link-intersect, anchor-diff, link-velocity, brand-mention, or competitor link-profile analysis for one target domain or URL.
brain-keeper
When the user wants to ingest sources, change brain pages, register decisions, catalog content publications, or lint brain pages for provenance and link integrity.
competitive-analysis
When the user wants to compare domains or URLs against competitors across SEO footprint, share of voice, keyword/content gap, head-to-head pages, off-page link gap (via backlink-analysis), and brand positioning. Orchestrates evidence from serp-extract, keyword-research, backlink-analysis, and topic-cluster without…
autoresearch
When the user wants a rigorous iteration loop for an artifact, prompt, briefing, content structure, or Agentic SEO skill. Also use for Karpathy-style experiment runs that need baseline scoring, explicit metrics, stop rules, and keep/reject decisions.
eeat
When the user wants to audit, strengthen, or prepare evidence for Experience, Expertise, Authoritativeness, and Trust. Also use before registering proof entries in project/brain/log.md or referencing them in project/brain/topic-clusters.md.