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.
git clone --depth 1 https://github.com/shalintripathi/organic-osWrote 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/agents/shalintripathi/organic-os/serp-ai-monitor)<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.
<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>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.00066 | $0.00448 |
| Opus 5 | $0.00033 | $0.00224 |
| Sonnet 5 | $0.00013 | $0.00090 |
| Haiku 4.5 | $0.00007 | $0.00045 |
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 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.
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:
- 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.
- 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).
- Locate the most recent prior runs/ folder for this routine and diff: position moves, snippet gained/lost, AI mention/citation gained/lost.
- Emit one drop or gain signal per notable movement; quiet queries need no signal beyond a rollup line.
- 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.
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.
- 12d ago First seen · 38 lines · 66 tokens per session scan A 67d4c8a10eb5
serp-ai-monitor is an agent published in the GitHub repository shalintripathi/organic-os (5 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 448 once invoked, about $0.0003 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 agents, from other repositories
ai-search-geo-specialist
Read-only AI-search (GEO/AEO) specialist. Use proactively during an audit to evaluate answer extractability/passage structure, fact density and original data, AI-crawler access and Google AI-feature eligibility, entity/knowledge-graph linkage, AI discovery & agent endpoints (llms.txt, agents.md, UCP, ai-catalog), and…
schema-generator
Structured-data specialist. Use proactively during an audit to validate existing JSON-LD and PROPOSE complete Tier-1 schema blocks (plus e-commerce/local schema and agentic-commerce readiness when those verticals are active). It proposes diffs only and does NOT write files.
seo-fixer-writer
The ONLY agent allowed to write files. Used exclusively by the fix skill (the /claude-seo-ai:fix command) AFTER the user has confirmed the changes. Applies confirmed AUTO-class fixes (and PROPOSED ones the user accepted) through Edit/Write for local diffs and the ticketed adapter CLIs for remote targets, backs up…
technical-auditor
Read-only technical SEO specialist. Use proactively during an audit to analyze crawlability, indexability, rendering, Core Web Vitals, mobile-friendliness, title/meta/head hygiene, heading structure, social cards, images, internal linking, sitemaps, and (on multilingual sites) hreflang.
content-eeat-analyst
Read-only content quality specialist. Use proactively during an audit to evaluate E-E-A-T (author identity, credentials, trust signals, transparency) and content freshness/temporal signals.
ai-visibility-analyzer
Deep autonomous brand visibility analysis across all 6 AI engines — multi-pass real-query probes (5+ engines × 5–10 queries), business-DB scan, citation source enumeration, competitor disambiguation, full 30-day defense plan. Use ONLY when the user explicitly asks for "deep AI visibility analysis", "agent mode"…