geo-visibility-check

geo-visibility-check is a skill for Claude Code from XPOZpublic/xpoz-agent-skills. It costs 94 tokens per session (3,035 once invoked), scanned A, original, MIT.

A one-time check of how often a brand appears in answers from Claude, ChatGPT, and Gemini for important buyer questions. GEO means improving a brand’s visibility in AI-generated answers.

In plain words
What is it for?
Use it for a quick AI-visibility or GEO audit of a brand, product, or category, including source and competitor comparisons.
Why use it?
It shows whether the brand is mentioned, which competitors appear instead, and what sources influence the answers.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code; built for openclaw.

Part of the xpoz plugin — 14 skills shipped together

Good fit Use it for a quick AI-visibility or GEO audit of a brand, product, or category, including source and competitor comparisons.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xpozpublic/xpoz-agent-skills/geo-visibility-check
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.

Any agent
npx skills add XPOZpublic/xpoz-agent-skills --skill geo-visibility-check
Clone the repo
git clone --depth 1 https://github.com/XPOZpublic/xpoz-agent-skills

Made for: Claude Code.

Or install xpoz, the plugin that ships this one along with the rest of its 14 skills.

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 geo-visibility-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/xpozpublic/xpoz-agent-skills/geo-visibility-check/github.svg)](https://agentmods.dev/skills/xpozpublic/xpoz-agent-skills/geo-visibility-check)
Your own site
<a href="https://agentmods.dev/skills/xpozpublic/xpoz-agent-skills/geo-visibility-check"><img src="https://agentmods.dev/badge/skills/xpozpublic/xpoz-agent-skills/geo-visibility-check/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 geo-visibility-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/xpozpublic/xpoz-agent-skills/geo-visibility-check"><img src="https://agentmods.dev/badge/skills/xpozpublic/xpoz-agent-skills/geo-visibility-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,035 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 2 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 5 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Data Exfiltration · line 51
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 311
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 51
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 311
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Agent Snooping · line 250
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
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.00094 $0.03035
Opus 5 $0.00047 $0.01517
Sonnet 5 $0.00019 $0.00607
Haiku 4.5 $0.00009 $0.00303

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

Security

Grade A, and why

geo-visibility-check scanned grade A with 2 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 2d 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.

import secrets, hashlib, base64, urllib.parse, json, urllib.request, os

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

subprocess.run(['mcporter', 'config', 'remove', 'xpoz'], capture_output=True)
skills/geo-visibility-check/SKILL.md · 302 lines

How it starts

The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GEO Visibility Check

Overview

Buyers increasingly start, and often finish, their research inside AI engines. This skill answers the first question of any GEO effort: for the questions that matter, does the brand appear in AI answers, and if not, who does and through which sources? It assembles a small panel of buyer prompts, runs each through the engines with full citation tracing, and delivers a per-prompt visibility verdict plus a read on where the winning answers come from. One-shot by design; it is the measurement pass that tells you whether a full GEO program is worth running.

When to Use

Activate when the user asks:

  • "Do AI assistants recommend [BRAND]?"
  • "Check our AI/GEO visibility"
  • "Where does [BRAND] show up in ChatGPT/Claude/Gemini answers?"
  • "Who wins [CATEGORY] in AI answers, and why?"
  • "Run a GEO audit for [PRODUCT]"
  • "Which sources do AI engines use for our category?"

Setup & Authentication

Before fetching data, ensure Xpoz access is configured. Follow these checks in order.

Check 1: Already authenticated?

If you have MCP tools, try calling any Xpoz tool (e.g., checkAccessKeyStatus). If it works → skip to Step 1.

If you have the SDK, try:

from xpoz import XpozClient
client = XpozClient()  # reads XPOZ_API_KEY env var

If this succeeds without error → skip to Step 1.

If neither works, you need to authenticate. Get a free access key (below).


Recommended: a free access key

Real analyses need a real key: get a free access key (free tier, up to 75K results, no credit card). SDK and CLI users set it as XPOZ_API_KEY; MCP connections sign in with the same account via OAuth on first tool call (paths below).


Path A: MCP via mcporter (OpenClaw agents)

If mcporter is available:

mcporter call xpoz.checkAccessKeyStatus

If hasAccessKey: true → ready. If not:

mcporter config add xpoz https://mcp.xpoz.ai/mcp --auth oauth

Then authenticate — generate the OAuth URL and send it to the user:

Read the full file on GitHub · 302 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. 2d ago Changed · -11 lines dbdd05239123
  2. 12d ago First seen · 313 lines · 94 tokens per session scan A a40fab8b6009

Subscribe to this mod's changes

geo-visibility-check is a skill published in the GitHub repository XPOZpublic/xpoz-agent-skills (15 stars, last pushed 3d ago), licensed MIT. It adds 94 tokens to every session and 3,035 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

git-workflow

This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…

Galaxy-Dawn/claude-scholar · 64 tokens

daily-paper-generator

Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.

Galaxy-Dawn/claude-scholar · 47 tokens

codex-autoresearch

Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…

leo-lilinxiao/codex-autoresearch · 80 tokens

clipboard

Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".

CodeAlive-AI/ai-driven-development · 36 tokens

neo4j-modeling-skill

Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…

neo4j-contrib/neo4j-skills · 152 tokens

git-commit

A Git assistant for reviewing local changes and creating conventional commit messages, which are standardized summaries of code changes. It can also run Git hooks and push the commit.

huangwb8/skills · 88 tokens