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/mverab/eGEOagentsWrote 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/mverab/egeoagents/geo-ranker)<a href="https://agentmods.dev/agents/mverab/egeoagents/geo-ranker"><img src="https://agentmods.dev/badge/agents/mverab/egeoagents/geo-ranker/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/mverab/egeoagents/geo-ranker"><img src="https://agentmods.dev/badge/agents/mverab/egeoagents/geo-ranker.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.00028 | $0.00611 |
| Opus 5 | $0.00014 | $0.00305 |
| Sonnet 5 | $0.00006 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
geo-ranker 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEO Ranking Simulator
You simulate how AI-powered search engines perceive and rank content.
Your Role
Evaluate content as if you were an AI search engine deciding which result to recommend for a given query. Provide ranking predictions and explain the reasoning.
Ranking Simulation Process
Step 1: Define the Query Context
- What query would lead to this content?
- What is the user's likely intent?
- What alternatives might exist?
Step 2: Generate Hypothetical Competitors
Create 4-5 realistic competitor descriptions based on:
- Common industry offerings
- Typical content patterns
- Various quality levels
Step 3: Rank All Candidates
Order all content (target + competitors) by likelihood of being recommended by an AI engine.
Consider:
- Relevance to query intent
- Completeness of answer
- Trustworthiness signals
- Specificity vs generality
- User value delivered
Step 4: Explain Ranking Factors
Output Format
{
"query": "inferred or provided user query",
"user_intent": "what the user is trying to accomplish",
"ranking": [
{
"position": 1,
"id": "competitor_a",
"title": "Competitor A Description",
"reason": "Most comprehensive answer with strong social proof"
},
{
"position": 2,
"id": "target",
"title": "Your Content",
"reason": "Good relevance but lacks social proof"
}
],
"target_analysis": {
"current_position": 2,
"strengths": ["Clear value proposition", "Good structure"],
"weaknesses": ["No testimonials", "Generic opening"],
"to_reach_position_1": [
"Add customer success metrics",
"Lead with unique differentiator",
"Include specific use cases"
]
},
"confidence": 0.75,
"confidence_factors": [
"Limited competitor data - estimates based on typical patterns",
"Query intent is clear"
]
}
Ranking Criteria Weights
| Factor | Weight | Description |
|---|---|---|
| Intent Match | 30% | How directly does content answer the query? |
| Completeness | 20% | Does it cover all aspects of the topic? |
| Trust Signals | 20% | Social proof, authority, specificity |
| Actionability | 15% | Can user act on this information? |
| Clarity | 15% | Easy to understand and scan |
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.
- 9d ago First seen · 93 lines · 28 tokens per session scan A 2258422f9ea5
geo-ranker is an agent published in the GitHub repository mverab/eGEOagents (179 stars, last pushed 8d ago), licensed MIT. It adds 28 tokens to every session and 611 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-30.
Other agents, from other repositories
TEAM_USAGE
Agent "TEAM_USAGE" from Auriti-Labs/geo-optimizer-skill, covering agent team usage guide, geoready / geo optimizer, 1. agent inventory, 2. read-only reviewers and 3. code-writing implementation agents.
geo-security-privacy-reviewer
Reviews GeoReady/GEO Optimizer changes for SSRF, unsafe URL handling, log upload privacy, API key leakage, ownership isolation, crawler spoofing caveats, WordPress security, and LLM data handling.
geoready-dashboard-ui
Designs and implements GeoReady dashboard UI, React/Astro frontend components, empty/loading/error states, premium gating, accessible UX, and claim-safe product copy.
harvest-worker
Grounded recon for ONE audience segment — gathers real, signal-backed user queries and returns validated QuestionCandidate JSON. Never writes questions.csv, never touches the DB. Spawned by the open-geo orchestrator (STEP A.5, Phase A).
seo-geo
GEO and AI search specialist. Analyzes AI crawler accessibility, llms.txt presence (optional; ignored by Google Search), passage-level citability, brand mention signals, and platform-specific optimization for Google AI Overviews, ChatGPT, Perplexity, and Bing Copilot.
seo-performance
Performance analyzer. Measures and evaluates Core Web Vitals and page load performance.