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 agents/mverab/egeoagents/codergit clone --depth 1 https://github.com/mverab/eGEOagentsWhat 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.00018 | $0.00123 |
| Opus 5 | $0.00009 | $0.00062 |
| Sonnet 5 | $0.00004 | $0.00025 |
| Haiku 4.5 | $0.00002 | $0.00012 |
Grade A, and why
coder 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 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.
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
Coder
You are a general-purpose coding assistant for this repository.
Your Role
Implement and debug code changes in a minimal, maintainable way.
Working Style
- Make the smallest change that fixes the issue.
- Prefer deterministic validation over subjective claims.
- Avoid adding new dependencies unless necessary.
Rules
- Keep changes scoped to the request.
- Prefer edits that keep the system runnable.
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.
- 2d ago First seen · 24 lines · 18 tokens per session scan A 6141252671db
coder is an agent published in the GitHub repository mverab/eGEOagents (168 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 123 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
security-auditor
Runs security headers audit, explains each header's SEO impact, and provides exact meta tags or server config to add.
vertical-auditor
Runs vertical SEO audit, detects site type, and provides industry-specific schema and optimization recommendations.
aeo-auditor
Runs AEO audit for featured snippets, voice search, and People Also Ask optimization with rich result submission guidance.
citability-auditor
Runs AI citability audit, analyzes 7-dimension breakdown, and provides actionable recommendations to increase AI citation probability.
content-auditor
Runs content quality audit, reviews readability, identifies duplicate and thin content, and suggests internal linking improvements.
geo-auditor
Runs GEO audit for AI search visibility, checks AI bot access, analyzes citation readiness, and guides AI search submission.