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/coder)<a href="https://agentmods.dev/agents/mverab/egeoagents/coder"><img src="https://agentmods.dev/badge/agents/mverab/egeoagents/coder/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/coder"><img src="https://agentmods.dev/badge/agents/mverab/egeoagents/coder.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.00018 | $0.00123 |
| Opus 5.5 | $0.00007 | $0.00049 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 24 lines · 18 tokens per session scan A 6141252671db
coder is an agent published in the GitHub repository mverab/eGEOagents (204 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 123 once invoked, about $0.0001 per session on Opus 5.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-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
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.
geo-wordpress-connector-architect
Designs the future lightweight WordPress connector for GeoReady, including API-key connection, site metadata, sitemap/CPT/WooCommerce/ACF detection, admin widget, security, and least-privilege architecture.
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).