seo-geo-report-engine: Skill for Claude Code

.agents/skills/rank-tracking/SKILL.md

rank-tracking is a skill for Claude Code from prashishh/seo-geo-report-engine. It costs 101 tokens per session (1,105 once invoked), scanned A, original, MIT.

A skill for recording and comparing search-engine rankings for tracked keywords over time. It reports meaningful gains, losses, search-result features, and competitor position changes.

In plain words
What is it for?
Use it to answer which keywords moved, whether a site ranks for a term, what dropped, and how competitors changed. It produces a rank report and updates a ranking-history CSV.
Why use it?
It shows which rankings genuinely moved instead of treating small fluctuations as important, using previous snapshots for comparison.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is prashishh/seo-geo-report-engine's own configuration. It tells Claude Code how to work on seo-geo-report-engine itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything seo-geo-report-engine configures →

Part of the seo-geo-report-engine plugin — 33 skills, 8 commands, 5 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to prashishh/seo-geo-report-engine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/prashishh/seo-geo-report-engine/main/.agents/skills/rank-tracking/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/prashishh/seo-geo-report-engine

Made for: Claude Code.

Or install seo-geo-report-engine, the plugin that ships this one along with the rest of its 33 skills, 8 commands, 5 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 rank-tracking

README.md
[![agentmods](https://agentmods.dev/badge/skills/prashishh/seo-geo-report-engine/rank-tracking/github.svg)](https://agentmods.dev/skills/prashishh/seo-geo-report-engine/rank-tracking)
Your own site
<a href="https://agentmods.dev/skills/prashishh/seo-geo-report-engine/rank-tracking"><img src="https://agentmods.dev/badge/skills/prashishh/seo-geo-report-engine/rank-tracking/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 rank-tracking

Your own site · 80×15
<a href="https://agentmods.dev/skills/prashishh/seo-geo-report-engine/rank-tracking"><img src="https://agentmods.dev/badge/skills/prashishh/seo-geo-report-engine/rank-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,105 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.
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.00101 $0.01105
Opus 5 $0.00051 $0.00553
Sonnet 5 $0.00020 $0.00221
Haiku 4.5 $0.00010 $0.00111

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

Security

Grade A, and why

rank-tracking 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 12d 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.

.agents/skills/rank-tracking/SKILL.md · 79 lines

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.

rank-tracking

Reads the client's Rank Tracker project, snapshots tracked positions, and reports what moved since the last snapshot — gains, losses, SERP features, and how competitors shifted. Output is research/rank-report.md plus an appended data/rank-history.csv. Ahrefs MCP is the engine (see knowledge/ahrefs-mcp-map.md).

Methodology is PERCEIVE → ANALYZE → VALIDATE → ACT. Every mover is falsifiable: state the term, prior position, current position, and the threshold (≥3 positions or a page-1 crossing) that makes it a real move vs noise.

Inputs

  • projects/<client>/client.ymldomain, competitors[], target_keywords[], market, and ahrefs.project_id (the Rank Tracker project). Resolve with ./bin/mkt config show --project <client>.
  • Prior data/rank-history.csv (the last snapshot you diff against).

Setup (first run)

If ahrefs.project_id is empty, list projects with management-projects, find the client's Rank Tracker project, and paste its id into client.yml under ahrefs.project_id. Confirm the tracked keyword set with management-project-keywords and competitors with management-project-competitors. Today is absolute (e.g. 2026-06-23); call doc on a tool before first use.

Workflow

1. PERCEIVE — pull current positions

  • rank-tracker-overview — current positions + distribution (top-3 / top-10 / top-100) for the project's tracked keywords.
  • management-project-keywords — confirm the tracked set (so a "lost" term isn't just untracked).
  • rank-tracker-serp-overview — SERP composition for key terms (which features appear: AI Overview, featured snippet, PAA, sitelinks, video).

2. ANALYZE — compute movers vs the last snapshot

  • Diff current positions against the most recent data/rank-history.csv snapshot.
  • Gained = improved ≥3 positions or entered top-10/top-3. Lost = dropped ≥3 or fell off page 1. Everything else = flat (don't report it as a move).
  • Note SERP-feature changes per term (gained/lost a snippet, AI Overview now present).

Read the full file on GitHub · 79 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. 12d ago First seen · 79 lines · 101 tokens per session scan A 9c75b77a7087

Subscribe to this mod's changes

rank-tracking is a skill published in the GitHub repository prashishh/seo-geo-report-engine (5 stars, last pushed 2mo ago), licensed MIT. It adds 101 tokens to every session and 1,105 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.

Related

Other skills, from other repositories

content-amplifier

Use when the user asks to "amplify influencer content with paid media", "set up whitelisting or Spark Ads", "decide which posts to boost", "repurpose influencer content", "turn one video into multiple ads", or "build a UGC asset library"; produces (paid mode) a content-selection scorecard, a paid amplification…

aaron-he-zhu/aaron-marketing-skills · 202 tokens

email-sequence-designer

Use when the user asks to "design a welcome flow", "set up an abandoned-cart sequence", "build a light re-engagement branch inside a lifecycle flow", or "plan a cold-outbound sequence"; produces general lifecycle automation flows (welcome, cart, browse-abandon, post-purchase, in-flow re-engagement, B2B cold outbound)…

aaron-he-zhu/aaron-marketing-skills · 197 tokens

reactivation-specialist

Use when the user asks to "build a win-back campaign", "re-engage lapsed subscribers", "run a re-permission / re-consent sweep", or "sunset my dead list"; produces a closed-loop reactivation program — a lapsed-cohort definition, a staged offer ladder, a re-consent (re-permission) capture step, and a sunset-confirm /…

aaron-he-zhu/aaron-marketing-skills · 215 tokens

campaign-planner

Use when the user asks to "plan an influencer campaign", "build a campaign blueprint", "track or close a creator campaign", or "record a late campaign correction"; produces the plan and, when requested, a non-canonical evidence tracker with scoped identity, publication, reconciliation, close, and reopen receipts. Not…

aaron-he-zhu/aaron-marketing-skills · 124 tokens

product-feed-optimizer

Use when the user asks to "optimize my Shopping feed", "fix product disapprovals", "improve product titles/attributes", or "build feed-driven PMax asset groups"; audits and rewrites the Shopping/Performance Max product feed — title/description patterns, required and recommended attributes, GTIN/availability/price…

aaron-he-zhu/aaron-marketing-skills · 144 tokens

attribution-reconciler

Use when platform-reported conversions disagree with GA4/ecommerce, when you suspect Meta and Google are double-counting the same sales, or for a standing (monthly) reconciliation workbook that de-dups stacked credit against an order-ID truth set, normalizes attribution windows and currency, compares attribution…

aaron-he-zhu/aaron-marketing-skills · 150 tokens