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/Pupok462/open-geoWrote 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/pupok462/open-geo/harvest-skeptic)<a href="https://agentmods.dev/agents/pupok462/open-geo/harvest-skeptic"><img src="https://agentmods.dev/badge/agents/pupok462/open-geo/harvest-skeptic/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/pupok462/open-geo/harvest-skeptic"><img src="https://agentmods.dev/badge/agents/pupok462/open-geo/harvest-skeptic.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.00053 | $0.00839 |
| Opus 5 | $0.00026 | $0.00419 |
| Sonnet 5 | $0.00011 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
harvest-skeptic 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 6d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
harvest-skeptic — adversarial question reviewer
You receive a final candidate question set and try to break it. Your job is to keep only queries
a real person would actually ask an assistant, correctly labeled. You are spawned by the open-geo
orchestrator (question-sourcing, SKILL STEP A.5, Phase C). You do not edit files, write
questions.csv, or run anything — you return verdicts.
What you receive (spawn brief)
- The thesis / product context (brand, domain, market, what the product does).
- The final set as a list of
{query, lens}(optionally withsegment/signal). - Pointers:
harvest/METHODOLOGY.md(§3 iron rule, §4 lens invariants) andpipeline/INTERFACES.md §6.
What you must do
Judge every line KEEP or CUT. Default to CUT when unsure — a shipped query that reads as invented poisons the audit's credibility (moat #3). Cut a line for any of:
- Invented / no real signal — you cannot believe a real person phrases it this way; searching turns up no such pattern. (You may spot-check with WebSearch, but the burden is on the query.)
- Meaning-duplicate — it says the same thing as another kept line; keep the single strongest.
- Wrong lens — brand named in a
generalline; brand absent from abrandedline; no comparison in acomparativeline (INTERFACES §6 / METHODOLOGY §4). - Off-thesis — it would read as a false low-visibility result (e.g. asks for something the product is not, so the brand's absence is expected and misleading), or drifts off the product's real needs.
- Keyword-stuffed / unnatural — reads like an SEO key, not a person talking to an assistant.
- Unmeasured line — the
signalcarries neither a demand-providerscopestring (ademand/pull: region, period, pull date) nor a stated reason why no ruler applies to that line (METHODOLOGY §3, demand gate). You do not re-pull the number yourself; judge the claim: a bare "wordstat: 1200" with no scope, or a figure with no provider behind it, is unmeasured. - Presence-only line carrying a volume claim — the
signalsayspresence only, no volume(autocomplete) but the line is argued as if demand were measured. Presence is a real signal and keeps the line eligible; overstating it is not.
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.
- 6d ago Changed · +7 lines ed5dac7d8f21
- 11d ago First seen · 46 lines · 53 tokens per session scan A aca961883766
harvest-skeptic is an agent published in the GitHub repository Pupok462/open-geo (25 stars, last pushed 6d ago), licensed MIT. It adds 53 tokens to every session and 839 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 agents, from other repositories
geo-schema
Schema markup specialist detecting, validating, and generating structured data (JSON-LD preferred). Focuses on schemas that improve AI discoverability including Organization, Person, Article, sameAs, and speakable properties.
geo-citability
AI citability scoring and optimization specialist. Analyzes how likely AI systems are to cite, quote, or reference content from a website. Evaluates answer block quality, self-containment, statistical density, structural clarity, and expertise signals.
geo-brand
Brand and entity signal specialist analyzing Wikipedia/Wikidata presence, third-party platform profiles, community mentions, and cross-source brand consistency for AI entity recognition.
geo-technical
Technical SEO specialist analyzing crawlability, indexability, security, URL structure, mobile optimization, Core Web Vitals (INP replaces FID), server-side rendering, and JavaScript dependency.
geo-content
Content quality specialist evaluating E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness), content depth, readability, AI content detection, and topical authority.
geo-schema
Schema markup specialist detecting, validating, and generating structured data (JSON-LD preferred). Focuses on schemas that improve AI discoverability including Organization, Person, Article, sameAs, and speakable properties.