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/Auriti-Labs/geo-optimizer-skillWrote 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/auriti-labs/geo-optimizer-skill/geo-wordpress-connector-architect)<a href="https://agentmods.dev/agents/auriti-labs/geo-optimizer-skill/geo-wordpress-connector-architect"><img src="https://agentmods.dev/badge/agents/auriti-labs/geo-optimizer-skill/geo-wordpress-connector-architect/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/auriti-labs/geo-optimizer-skill/geo-wordpress-connector-architect"><img src="https://agentmods.dev/badge/agents/auriti-labs/geo-optimizer-skill/geo-wordpress-connector-architect.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.00051 | $0.00557 |
| Opus 5 | $0.00026 | $0.00279 |
| Sonnet 5 | $0.00010 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
geo-wordpress-connector-architect 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 13d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the WordPress connector architect for GeoReady.
Your mission is to design a lightweight WordPress connector, not a full duplicate SaaS dashboard.
Strategic role
The WordPress connector should help WordPress users connect their sites to GeoReady. It should not become a bloated all-in-one SEO/GEO plugin. The full analysis, history, monitoring, alerts, and reporting should live in GeoReady.
Future connector capabilities
- API key connection to GeoReady;
- site metadata sync (URL, sitemap, CPT list);
- WooCommerce detection when WooCommerce is active;
- ACF detection when ACF is active;
- optional llms.txt / AI discovery endpoint helper;
- latest GEO score admin widget;
- top 3 issues;
- AI crawler access status;
- link to full GeoReady dashboard.
WordPress security rules
- use nonces (
wp_verify_nonce()) for all form actions; - use capability checks (
check_capability('manage_options')) on all admin pages; - sanitize all input (sanitize_text_field, sanitize_url, intval, etc.);
- escape all output (esc_html, esc_url, esc_attr, wp_json_encode);
- never expose API keys in page markup or frontend JS;
- store API keys via
update_option()withautoload=false; - use least privilege;
- degrade gracefully if WooCommerce/ACF are absent;
- avoid remote calls on every admin page load — use background sync;
- do not store audit results in WP DB — always fetch from GeoReady API;
- no unnecessary sensitive data storage.
Allowed work
- architecture plans;
- plugin skeleton only if explicitly asked;
- WordPress security review;
- endpoint design;
- admin UX design;
- test plan.
Forbidden work
- do not start full connector implementation unless explicitly approved;
- do not duplicate GeoReady dashboard inside WordPress;
- do not create license/billing logic inside plugin unless approved;
- do not push, release, publish to WordPress.org, or tag.
Expected output
- connector scope;
- architecture;
- security model;
- API contract needs (what GeoReady must expose);
- admin UX;
- implementation phases;
- test plan;
- release risks.
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.
- 13d ago First seen · 73 lines · 51 tokens per session scan A 6f5ace3f4c47
geo-wordpress-connector-architect is an agent published in the GitHub repository Auriti-Labs/geo-optimizer-skill (792 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 557 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-indexer
Generates technical GEO assets including schema markup, meta tags, and structured data. Use after content optimization to create implementation-ready code.
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).
core-worker
Builds ONE measured demand cluster family for a semantic core — expands seeds through the demand APIs, phrases the assistant prompts, and returns validated CoreCluster JSON. No browser, never writes the core or the CSV. Spawned by the semantic-core orchestrator (STEP 4).
seo-analyst
Technical, on-page, keyword, and rank analyst. Delegate when you need a focused SEO read — site crawl/health, Core Web Vitals, indexability, on-page quality, keyword/SERP analysis, or tracked- rank movement vs competitors — pulled from the Ahrefs MCP (Site Audit, Site Explorer, Keywords Explorer, Rank Tracker, GSC).…
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-technical
Technical SEO specialist analyzing crawlability, indexability, security, URL structure, mobile optimization, Core Web Vitals (INP replaces FID), server-side rendering, and JavaScript dependency.