serp-ai-monitor

serp-ai-monitor is an agent for Claude Code from shalintripathi/organic-os. It costs 66 tokens per session (448 once invoked), scanned A, original, MIT.

A search-visibility monitoring agent that checks where a site appears in Google results and AI answers for selected keywords. It compares the current results with earlier runs.

In plain words
What is it for?
Use it to monitor keyword positions, featured snippets, Google’s “People Also Ask” results, and whether AI search tools mention or link to a site. It also produces findings and movement signals from the comparison.
Why use it?
It removes the need to check search rankings and AI mentions manually each week. It highlights important gains and losses, such as leaving page one or losing an AI citation.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the organic-os plugin — 24 skills, 24 commands, 14 agents, 2 hooks shipped together

Good fit Use it to monitor keyword positions, featured snippets, Google’s “People Also Ask” results, and whether AI search tools mention or link to a site. It also produces findings and movement signals from the comparison.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/shalintripathi/organic-os/serp-ai-monitor
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.

Clone the repo
git clone --depth 1 https://github.com/shalintripathi/organic-os

Made for: Claude Code.

Or install organic-os, the plugin that ships this one along with the rest of its 24 skills, 24 commands, 14 agents, 2 hooks.

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 serp-ai-monitor

README.md
[![agentmods](https://agentmods.dev/badge/agents/shalintripathi/organic-os/serp-ai-monitor/github.svg)](https://agentmods.dev/agents/shalintripathi/organic-os/serp-ai-monitor)
Your own site
<a href="https://agentmods.dev/agents/shalintripathi/organic-os/serp-ai-monitor"><img src="https://agentmods.dev/badge/agents/shalintripathi/organic-os/serp-ai-monitor/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 serp-ai-monitor

Your own site · 80×15
<a href="https://agentmods.dev/agents/shalintripathi/organic-os/serp-ai-monitor"><img src="https://agentmods.dev/badge/agents/shalintripathi/organic-os/serp-ai-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 448 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.00066 $0.00448
Opus 5.5 $0.00026 $0.00179
Sonnet 5.5 $0.00013 $0.00090
Haiku 4.5 $0.00007 $0.00045

Measured 2mo ago against content hash 67d4c8a10eb5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

serp-ai-monitor 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 2mo 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.

plugin/agents/serp-ai-monitor.md · 38 lines

What it actually says

You are the SERP and AI-visibility monitor on an organic-growth team.

Input contract: the prompt gives you (1) the path to site-profile.yaml, (2) the target URL(s) and prior run artifacts under runs/ if available. Read the profile first; use its keywords.targets as the query set.

Method:

  1. For each target keyword (cap per run per the profile's rotation), check current Google SERP presence for the site's URLs: position band, featured snippet, People Also Ask presence.
  2. Run the same query set through available AI engines (an authorized AI-search connector, or WebSearch with engine-targeted queries). Record whether the site is mentioned and whether it is cited (linked).
  3. Locate the most recent prior runs/ folder for this routine and diff: position moves, snippet gained/lost, AI mention/citation gained/lost.
  4. Emit one drop or gain signal per notable movement; quiet queries need no signal beyond a rollup line.
  5. Flag any P1 movement (a money-page keyword losing its AI citation or dropping out of page 1) prominently in Findings.

Output contract (return exactly this shape):

Findings

  • one bullet per finding: [severity P0-P3] observation - evidence URL/line

Signals

  • one line per signal worth tracking, each with: observation | why it matters | falsifiability ("we are wrong if...") | leading indicator to watch

Proposed fixes

  • one bullet per fix: target URL | change | expected effect | effort S/M/L

Never invent metrics. If a check needs a credential the environment lacks, say "skipped: (needs )" instead of guessing.

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. 2mo ago First seen · 38 lines · 66 tokens per session scan A 67d4c8a10eb5

Subscribe to this mod's changes

serp-ai-monitor is an agent published in the GitHub repository shalintripathi/organic-os (7 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 448 once invoked, about $0.0003 per session on Opus 5.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

serp-ai-monitor compared with agents from other repositories

serp-ai-monitor next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
serp-ai-monitorshalintripathi/organic-osAgent71mo agoMITA66Claude Code
seo-auditorakii-technologies-ltd/akii-seo-ai-search-optimizerAgent795d agoMITA90Claude Code
ai-visibility-analyzerakii-technologies-ltd/akii-seo-ai-search-optimizerAgent795d agoMITA0Claude Code
competitor-analyzerakii-technologies-ltd/akii-seo-ai-search-optimizerAgent795d agoMITA120Claude Code
content-strategistakii-technologies-ltd/akii-seo-ai-search-optimizerAgent795d agoMITA122Claude Code
schema-generatorakii-technologies-ltd/akii-seo-ai-search-optimizerAgent795d agoMITA124Claude Code
ai-search-geo-specialistHainrixz/claude-seo-aiAgent8313d agoMITA81Claude Code