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.
npx agentmods add commands/mverab/egeoagents/geo-batchgit 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/commands/mverab/egeoagents/geo-batch)<a href="https://agentmods.dev/commands/mverab/egeoagents/geo-batch"><img src="https://agentmods.dev/badge/commands/mverab/egeoagents/geo-batch.svg" alt="Measured on agentmods" 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 | $0.00011 | $0.00231 |
| Opus 5 | $0.00005 | $0.00115 |
| Sonnet 5 | $0.00002 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
geo:batch 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 4d 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
/geo:batch Command
Batch process all content files in a folder.
Workflow
- Validate MCPs - Run
validation-doctor; if missing, provide setup snippets - Scan - Find all matching files in folder
- Process - Run
/geo:optimizeon each file (analyzer-based) - Summarize - Generate batch report
Output
For each file:
- Optimized version in
geo-output/optimized/ - Schema in
geo-output/schema/
Summary report with:
- Files processed
- Average score improvement
- Top priority fixes across all content
Example Usage
/geo:batch ./content
/geo:batch ./pages --pattern "*.html"
/geo:batch ./blog
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.
- 4d ago First seen · 42 lines · 11 tokens per session scan A 6db49a08a80c
geo:batch is a command published in the GitHub repository mverab/eGEOagents (172 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 231 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 commands, from other repositories
rank-compete
Competitive X-Ray. Compare your site's SEO signals, tech stack, content depth, and conversion patterns against any competitor URL.
rank-perf
Performance and mobile-first indexing audit from HTML — no Chrome needed.
rank-citability
Score how likely AI search engines are to cite your content.
rank-security
Security headers and HTTPS compliance audit for SEO.
rank
SEO/GEO/AEO audit, analysis, and optimization. The most comprehensive search toolkit for Claude Code.
rank-audit
Full SEO/GEO/AEO audit with auto-fix. Scans, reports, fixes, and verifies.