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/XuanRanL/loamwright-SEO-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/xuanranl/loamwright-seo-skill/audit-google)<a href="https://agentmods.dev/agents/xuanranl/loamwright-seo-skill/audit-google"><img src="https://agentmods.dev/badge/agents/xuanranl/loamwright-seo-skill/audit-google.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.1 | $0.00032 | $0.01016 |
| Opus 5 | $0.00016 | $0.00508 |
| Sonnet 5 | $0.00006 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
audit-google 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 8d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Google Agent
Spawn Condition
At least one Google credential configured in {audit_dir}/config.json :: api_keys — google_crux, google_gsc, or google_ga4. Skip unavailable sources gracefully.
Inputs
{audit_dir}/config.json— API keys, domain, GSC property URL, GA4 property ID{audit_dir}/crawl-results.json— URL list for per-page CrUX lookups
Scripts
python -m scripts.audit.pagespeed_check {url} --crux-only --json(URL is positional)python -m scripts.audit.google_oauth_setup— ONE-TIME interactive OAuth authorization for GSC + GA4 (opens a browser; no flags, no--json). Run only if~/.xuanran-seo/credentials/google-oauth-token.jsonis missing;gsc_fetch/ga4_fetchread the stored token themselves.python -m scripts.audit.gsc_fetch --property {siteUrl} --days {N} --jsonpython -m scripts.audit.ga4_fetch --property-id {id} --metrics sessions,totalUsers --days {N} --json
Checks
CrUX Field CWV (if crux key)
Origin-level + top-10 page-level 75th-percentile metrics. Thresholds — LCP: good < 2.5s, poor > 4.0s; INP: good < 200ms, poor > 500ms; CLS: good < 0.1, poor > 0.25. Report by form factor (mobile = ranking signal). 25-week trend via linear regression: improving/stable/declining. CRITICAL if any mobile metric poor; HIGH if needs-improvement; HIGH for active regression crossing good→needs-improvement in 8 weeks.
GSC Indexation (if gsc key)
Indexed pages count vs total excluded. Indexation ratio target > 85% (HIGH if < 70%, CRITICAL if < 50%). Top 5 exclusion reasons by count. Sitemap submission gap: in-sitemap but not-indexed pages. Coverage errors: 5xx, 4xx from Googlebot. "Crawled currently not indexed" > 20% = HIGH.
GSC Query Performance (if gsc key)
Top 20 queries by impressions (28d). Branded vs non-branded avg position. High-impression low-CTR queries (title/desc opportunity). Position distribution: % in 1-3, 4-10, 11-20, 20+. Biggest impression changes vs prior 28d.
GA4 Organic Traffic (if ga4 key)
30/90/180-day organic sessions. MoM and QoQ trend %. Top 10 landing pages by organic sessions. Bounce rate and pages/session for organic segment. HIGH if QoQ decline > 20%; MEDIUM if 10-20%.
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.
- 8d ago First seen · 55 lines · 32 tokens per session scan A ecce604e1c83
audit-google is an agent published in the GitHub repository XuanRanL/loamwright-SEO-Skill (47 stars, last pushed 21d ago), licensed Apache-2.0. It adds 32 tokens to every session and 1,016 once invoked, about $0.0002 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
schema-generator
Structured-data specialist. Use proactively during an audit to validate existing JSON-LD and PROPOSE complete Tier-1 schema blocks (plus e-commerce/local schema and agentic-commerce readiness when those verticals are active). It proposes diffs only and does NOT write files.
seo-fixer-writer
The ONLY agent allowed to write files. Used exclusively by the fix skill (the /claude-seo-ai:fix command) AFTER the user has confirmed the changes. Applies confirmed AUTO-class fixes (and PROPOSED ones the user accepted) through Edit/Write for local diffs and the ticketed adapter CLIs for remote targets, backs up…
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.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.