voyage-geo-agent: Instructions file for Codex

AGENTS.md

voyage-geo-agent AGENTS.md is an instructions file for Codex, OpenCode from onvoyage-ai/voyage-geo-agent. It costs 1,271 tokens per session, scanned A, original, MIT.

Installation instructions for Voyage GEO, a Python tool that analyzes how brands appear in answers from generative AI systems. GEO, or generative engine optimization, means improving a brand’s visibility in those answers.

In plain words
What is it for?
Use them to set up Voyage GEO, test provider connections, run brand audits or leaderboards, and export reports in formats such as HTML, JSON, CSV, or Markdown.
Why use it?
They describe how to install the tool, create its agent skill, check configured providers, and run brand or category analyses.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions Claude Code; built for openclaw.

This is onvoyage-ai/voyage-geo-agent's own configuration. It tells Codex and OpenCode how to work on voyage-geo-agent 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 voyage-geo-agent configures →

Reuse

Borrowing it

Nothing to install: this file belongs to onvoyage-ai/voyage-geo-agent. 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/onvoyage-ai/voyage-geo-agent/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/onvoyage-ai/voyage-geo-agent

Made for: Codex, OpenCode.

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 voyage-geo-agent AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/onvoyage-ai/voyage-geo-agent/agents-md/github.svg)](https://agentmods.dev/instructions/onvoyage-ai/voyage-geo-agent/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/onvoyage-ai/voyage-geo-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/onvoyage-ai/voyage-geo-agent/agents-md/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 voyage-geo-agent AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/onvoyage-ai/voyage-geo-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/onvoyage-ai/voyage-geo-agent/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,271 This file is loaded in full into every session.
When invoked 1,271 The same file — it is already loaded in full.
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.01271 $0.01271
Opus 5 $0.00635 $0.00635
Sonnet 5 $0.00254 $0.00254
Haiku 4.5 $0.00127 $0.00127

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

Security

Grade A, and why

voyage-geo-agent AGENTS.md 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.md · 128 lines

How it starts

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

Voyage GEO — Install Instructions for AI Agents

You are an AI agent. Follow these steps exactly to install Voyage GEO for your user.

1. Install the Python package

pip install voyage-geo

2. Create the skill file

Create this one all-in-one skill file. Detect your platform:

  • OpenClaw: write to ~/.openclaw/skills/
  • Claude Code: write to .claude/skills/ in the current project

File: voyage-geo-aeo-analysis/SKILL.md

---
name: voyage-geo-aeo-analysis
description: Run complete GEO analysis workflows with voyage-geo, including both brand runs and category leaderboards
user_invocable: true
---

# voyage-geo-aeo-analysis

You are an AI brand analyst running Generative Engine Optimization (GEO/AEO) audits. Guide the user through setup, execution, and interpretation for both brand analysis and category leaderboard workflows.

## CLI Reference

pip install voyage-geo                     # install if needed
voyage-geo providers                       # list configured providers
voyage-geo providers --test                # health check providers
voyage-geo run -b "<name>" -w "<url>" -p chatgpt,gemini,claude -f html,json,csv,markdown
voyage-geo leaderboard "<category>" -p chatgpt,gemini,claude -q 20 --stop-after query-generation
voyage-geo leaderboard "<category>" --resume <run-id> -p chatgpt,gemini,claude -f html,json,csv,markdown

## Step 1: Validate Setup & Providers

1. Check if voyage-geo is installed. If not: `pip install voyage-geo`
2. Run voyage-geo providers to see which API keys are configured.
3. Present available models and ask the user which ones to include:
   - ChatGPT (OPENROUTER_API_KEY or OPENAI_API_KEY)
   - Claude (OPENROUTER_API_KEY or ANTHROPIC_API_KEY)
   - Gemini (OPENROUTER_API_KEY or GOOGLE_API_KEY)
   - Perplexity (OPENROUTER_API_KEY or PERPLEXITY_API_KEY)
   - DeepSeek (OPENROUTER_API_KEY)
   - Grok (OPENROUTER_API_KEY)
   - Llama (OPENROUTER_API_KEY)
   - Mistral (OPENROUTER_API_KEY)
   - Cohere (OPENROUTER_API_KEY)
   - Qwen (OPENROUTER_API_KEY)
   - Kimi (OPENROUTER_API_KEY)
   - GLM (OPENROUTER_API_KEY)
   Tip: OpenRouter (https://openrouter.ai/keys) gives access to all models with one key.
4. After the user picks models, check which API keys are missing.
   - If keys are missing, ask the user to provide them.
   - Write keys to .env file. NEVER echo keys back to the user.
5. Check the Processing provider line in the voyage-geo providers output.
   - If it says "configured" — good, proceed.
   - If it says "NOT CONFIGURED" — the user needs at least one of: ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, or OPENROUTER_API_KEY.
6. Verify with voyage-geo providers --test
7. Confirm the final model list with the user before proceeding.

## Step 2: Choose Workflow

Ask which workflow they want:
- `brand-run` (single brand GEO analysis)
- `leaderboard` (category-wide GEO ranking)

## Step 3A: Run `brand-run`

Ask:
1. "What brand do you want to analyze?" (required)
2. "What's the website URL?" (optional but recommended)
3. "Who are the main competitors?" (optional)
4. "Any specific keywords or product categories to focus on?" (optional)

Do NOT proceed until you have at least the brand name.

Summarize the analysis plan, then run:
voyage-geo run -b "<name>" -w "<url>" -p <list> -q <n> -f html,json,csv,markdown

After the run completes:
1. Read data/runs/<run-id>/analysis/summary.json
2. Read data/runs/<run-id>/analysis/analysis.json
3. Present key findings conversationally: mention rate, sentiment, mindshare rank, provider comparison
4. Present narrative analysis: brand themes, USP coverage gaps, competitor themes
5. Highlight recommendations
6. Tell them where the HTML report is

## Step 3B: Run `leaderboard`

Ask:
1. "What category do you want to rank?" (required)
2. "Any specific provider set, query count, or max brands?" (optional)

Do NOT proceed without a category.

Run query generation first:
voyage-geo leaderboard "<category>" -p <list> -q <n> --stop-after query-generation

Then:
1. Read data/runs/<run-id>/queries.json
2. Present queries in a table for user review
3. Resume full execution:
voyage-geo leaderboard "<category>" --resume <run-id> -p <list> -f html,json,csv,markdown

After completion:
1. Read data/runs/<run-id>/analysis/leaderboard.json
2. Present rankings table
3. Highlight #1, biggest gaps, provider preferences, surprises
4. Tell them where the HTML report is

Ask at the end:
"Want to dig deeper into any findings or rerun with different providers/queries?"

Read the full file on GitHub · 128 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 · 128 lines · 1,271 tokens per session scan A 3efb14671693

Subscribe to this mod's changes

voyage-geo-agent AGENTS.md is an instructions file published in the GitHub repository onvoyage-ai/voyage-geo-agent (382 stars, last pushed 6mo ago), licensed MIT. It adds 1,271 tokens to every session, about $0.0064 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-30.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,126 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens