What is geo-discovery?

A website audit command that checks machine-readable files and markup used by search engines and AI systems to understand a site.

It checks llms.txt, agents.json, robots.txt, JSON-LD, sitemap.xml, and FAQ schema, then reports fixes and can provide copy-ready schema content.

It shows which discovery files or structured data are missing, invalid, blocked, or incomplete, so you do not have to inspect each one manually.

geo-discovery — Command for Claude Code by studiomeyer-io

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/studiomeyer-io/studiomeyer-marketplace

Made for: Claude Code.

Or install studiomeyer-geo, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 1 agent.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/geo-discovery/github.svg)](https://agentmods.dev/commands/studiomeyer-io/studiomeyer-marketplace/geo-discovery)

Your own site

<a href="https://agentmods.dev/commands/studiomeyer-io/studiomeyer-marketplace/geo-discovery"><img src="https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/geo-discovery/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/studiomeyer-io/studiomeyer-marketplace/geo-discovery"><img src="https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/geo-discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 268 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.

Model	Per session	Once invoked
Fable 5.1	$0.00028	$0.00268
Opus 5	$0.00014	$0.00134
Sonnet 5	$0.00006	$0.00054
Haiku 4.5	$0.00003	$0.00027

Measured 6d ago against content hash 15540605c636, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

geo-discovery 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 6d 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.

plugins/studiomeyer-geo/commands/geo-discovery.md · 24 lines

What it actually says

Run a full discovery stack audit on $ARGUMENTS.

Call geo_discovery_stack with url: "$ARGUMENTS". This covers:
- llms.txt (presence + validity)
- agents.json (presence + AI capability declaration)
- robots.txt (AI bot allow/block matrix)
- JSON-LD (Organization, WebSite, FAQPage schemas)
- sitemap.xml (present, reachable, URL count)
- FAQ schema (present, properly marked up)
Also call geo_json_ld_audit to validate recommended properties per schema type.
Present a checklist format:
- ✅ llms.txt: present and valid
- ❌ agents.json: missing
- ⚠️ robots.txt: ClaudeBot blocked
- ...
For each failed or warning item, provide the specific fix with exact copy-paste content where possible (geo_schema_generator can generate missing JSON-LD blocks).

This command is the fastest way to get AI-ready because it skips the expensive LLM pings and focuses on machine-verifiable signals.

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.

6d ago Changed · -1 tokens per session 15540605c636
11d ago First seen · 24 lines · 29 tokens per session scan A 694e3caab930

Subscribe to this mod's changes

geo-discovery is a command published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 6d ago), licensed MIT. It adds 28 tokens to every session and 268 once invoked, about $0.0001 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.

Claude Code Marketing and SEO agent-personas ai-memory claude-code-plugin crm geo

geo-discovery

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

status

open

visibly-seo-potential

visibly-seo-status-quo

visibly-seo-offer

seo-fix