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 skills/mverab/egeoagents/geo-loopnpx skills add mverab/eGEOagents --skill geo-loopgit 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/skills/mverab/egeoagents/geo-loop)<a href="https://agentmods.dev/skills/mverab/egeoagents/geo-loop"><img src="https://agentmods.dev/badge/skills/mverab/egeoagents/geo-loop.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.00062 | $0.01580 |
| Opus 5 | $0.00031 | $0.00790 |
| Sonnet 5 | $0.00012 | $0.00316 |
| Haiku 4.5 | $0.00006 | $0.00158 |
Grade A, and why
geo-loop 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 5d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEO Loop Skill
One wake-up = one bounded unit of work. This skill governs loop mode only;
one-shot /geo <url> is unchanged and needs no workspace.
Non-negotiables
- Never write to the eGEOagents repo tree. Every write goes to the
workspace resolved from
$EGEO_HOME(default~/.egeo/). - One unit of work per run. Take the domain's
## Current focus, or the first Backlog item if focus is already satisfied. Do not batch. - Exactly one Timeline entry and exactly one LOG.md line per run.
- Write, then verify. Re-read every file you wrote before exiting.
- Never fabricate. Rankings, competitors, and metrics come from collector
JSONL under
data/or from a tool call in this session. A claim you cannot cite isconfidence: lowwith the uncertainty stated in the body. - Append-only history. Never edit or delete an existing Timeline entry or LOG line.
Procedure
1. Resolve the plan
egeo loop run <domain> --dry-run
This is the source of truth for the run: it prints the charter's current focus,
the backlog, collector records added since the last Timeline entry, and
candidate signals. It writes nothing. Use --json when you want to parse it.
If it exits non-zero, stop and report — the workspace or the domain charter is
not in a runnable state (egeo loop doctor explains why).
2. Read the state
$EGEO_HOME/domains/<domain>/README.md— charter, cadence, focus, backlog, Timeline (the last entry tells you where the previous run stopped).$EGEO_HOME/project.yaml— when present, the validated project identity, canonical domain, tracked queries/pages, and anti-spam/canibalization guardrails.egeo loop doctoris the source of truth for its validity.$EGEO_HOME/data/<collector>/*.jsonl— fresh ground truth.$EGEO_HOME/signals/and$EGEO_HOME/docs/— what is already known, so you dedupe instead of duplicating.$EGEO_HOME/config.yaml— models, budgets,reflect.auto_apply.$EGEO_HOME/data/outcomes/ledger.jsonl— append-only decision outcomes whenegeo loop decidehas run.
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.
- 5d ago First seen · 149 lines · 62 tokens per session scan A 20aed533b685
geo-loop is a skill published in the GitHub repository mverab/eGEOagents (173 stars, last pushed 4d ago), licensed MIT. It adds 62 tokens to every session and 1,580 once invoked, about $0.0003 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 skills, from other repositories
content-amplifier
Use when the user asks to "amplify influencer content with paid media", "set up whitelisting or Spark Ads", "decide which posts to boost", "repurpose influencer content", "turn one video into multiple ads", or "build a UGC asset library"; produces (paid mode) a content-selection scorecard, a paid amplification…
outreach-manager
Use when the user asks to "write influencer outreach", "follow up with a creator", "pitch a journalist, hunter, or launch partner", or "negotiate partnership terms"; produces personalized pitches, multi-touch follow-up sequences, negotiation scripts with objection handling, and a status pipeline tracker — the shared…
campaign-planner
Use when the user asks to "plan an influencer campaign", "build a campaign blueprint", "track or close a creator campaign", or "record a late campaign correction"; produces the plan and, when requested, a non-canonical evidence tracker with scoped identity, publication, reconciliation, close, and reopen receipts. Not…
cold-outbound-sequencer
Use when the user asks to "build a B2B cold-outbound sequence", "design reply-triage branching", "plan a domain warmup / sending throttle", or "make my outbound CAN-SPAM / opt-in compliant"; produces a multi-step outbound sequence with reply-triage branches (positive / objection / referral / not-now / opt-out), a…
inbox-placement-monitor
Use when the user asks to "track where my emails are actually landing after I send", "read my seed-list inbox vs spam vs promotions results", "trend my Gmail Postmaster / Microsoft SNDS reputation", or "did placement drop after my last send"; produces a per-provider inbox/spam/promotions placement read, a domain/IP…
send-experiment-designer
Use when the user asks to "design an email A/B test", "set up a multivariate subject/CTA test", "run a send-time test", "build a hold-out group", or "is this email result statistically and practically material?"; produces a falsifiable hypothesis, one-variable-per-cell matrix, sample-size/MDE/duration/power plan, and…