creo-gsc

creo-gsc is an agent for Claude Code from oyusypenko/creo. It costs 51 tokens per session (2,550 once invoked), scanned A, original, MIT.

An analysis agent for Google Search Console and website search-engine checks. Google Search Console is Google's service for monitoring indexing, search traffic, and site issues; some checks use its API and others use the browser interface.

In plain words
What is it for?
Use it to check security headers, page structure, structured data, language links, robots.txt, sitemaps, content, mobile behavior, performance, and Search Console indexing or search reports.
Why use it?
It can investigate both public page details and account-specific Search Console data, including information unavailable through the API. This avoids treating a basic page check as a complete SEO audit.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the creo plugin — 19 skills, 17 agents shipped together

Good fit Use it to check security headers, page structure, structured data, language links, robots.txt, sitemaps, content, mobile behavior, performance, and Search Console indexing or search reports.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/oyusypenko/creo/creo-gsc
Install

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.

Clone the repo
git clone --depth 1 https://github.com/oyusypenko/creo

Made for: Claude Code.

Or install creo, the plugin that ships this one along with the rest of its 19 skills, 17 agents.

Wrote 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.

agentmods badge for creo-gsc

README.md
[![agentmods](https://agentmods.dev/badge/agents/oyusypenko/creo/creo-gsc/github.svg)](https://agentmods.dev/agents/oyusypenko/creo/creo-gsc)
Your own site
<a href="https://agentmods.dev/agents/oyusypenko/creo/creo-gsc"><img src="https://agentmods.dev/badge/agents/oyusypenko/creo/creo-gsc/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.

agentmods 80×15 button for creo-gsc

Your own site · 80×15
<a href="https://agentmods.dev/agents/oyusypenko/creo/creo-gsc"><img src="https://agentmods.dev/badge/agents/oyusypenko/creo/creo-gsc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,550 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.02550
Opus 5 $0.00026 $0.01275
Sonnet 5 $0.00010 $0.00510
Haiku 4.5 $0.00005 $0.00255

Measured 10d ago against content hash eb8d77842d82, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

creo-gsc scanned grade A with 1 finding 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 10d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

3. Live-check the newest-crawled rows with `curl -sIL <url>` before filing
extensions/gsc-analyzer/agents/creo-gsc.md · 231 lines

How it starts

The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GSC Analyzer Agent

You are the Creo GSC subagent. You run Google Search Console analysis and SEO audits using the gsc_toolkit Python package.

Setup

The gsc_toolkit package is installed at ${HOME}/.claude/skills/creo-gsc/gsc_toolkit/.

Before running any command, activate the environment:

GSC_DIR="${HOME}/.claude/skills/creo-gsc"
source "${GSC_DIR}/.venv/bin/activate" 2>/dev/null || true
export PYTHONPATH="${GSC_DIR}:${PYTHONPATH}"

Available Commands

No API required (page analysis)

These work on any public URL without credentials:

python -m gsc_toolkit security <url>        # Security headers
python -m gsc_toolkit onpage <url>           # On-page SEO
python -m gsc_toolkit schema <url>           # Structured data
python -m gsc_toolkit hreflang <url>         # Hreflang validation
python -m gsc_toolkit robots <base_url>      # robots.txt
python -m gsc_toolkit sitemap-check <url>    # Sitemap XML
python -m gsc_toolkit content <url>          # Content quality
python -m gsc_toolkit mobile <url>           # Mobile SEO
python -m gsc_toolkit performance <url>      # Performance
python -m gsc_toolkit url-analysis <url>     # URL structure
python -m gsc_toolkit full-seo <url>         # All 9 analyzers
python -m gsc_toolkit site-audit <url>       # Crawl + audit

API required (Google service account needed)

python -m gsc_toolkit list-sites
python -m gsc_toolkit inspect <url>
python -m gsc_toolkit analytics [--days 28]
python -m gsc_toolkit sitemaps
python -m gsc_toolkit cwv <url>
python -m gsc_toolkit index-request <url>
python -m gsc_toolkit seo-audit [--days 28]
python -m gsc_toolkit full-report [--days 28]

Execution Guidelines

  1. Always activate the venv/PYTHONPATH before running commands.
  2. For full-seo analysis, the command runs all 9 analyzers automatically.
  3. For site-audit, suggest reasonable limits: --max-pages 100 for quick audits, --max-pages 500 for thorough ones.
  4. If a GSC API command fails with auth errors, inform the user they need to configure a Google service account.
  5. Present results clearly. Highlight critical issues first, then warnings, then recommendations.
  6. When the user asks for a "site audit" or "SEO check", determine whether they want:
    • A single page analysis: use full-seo <url>
    • A site-wide crawl: use site-audit <url>
    • GSC data review: use seo-audit

Read the full file on GitHub · 231 lines

Changes

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.

  1. 10d ago First seen · 231 lines · 51 tokens per session scan A eb8d77842d82

Subscribe to this mod's changes

creo-gsc is an agent published in the GitHub repository oyusypenko/creo (4 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 2,550 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other agents, from other repositories

devops-architect

DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…

closedloop-ai/claude-plugins · 95 tokens

whitepaper-coherence

Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.

FlorianBruniaux/claude-code-ultimate-guide · 39 tokens

hydra-runner

🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…

AR6420/Hail_Hydra · 105 tokens

code-reviewer

An AI code-review assistant that checks changed code for architecture, quality, type safety, error handling, security, and project-rule compliance. Its instructions and output format are written in Chinese.

xiaobei930/cc-best · 74 tokens

security-auditor

Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…

HermeticOrmus/LibreUIUX-Claude-Code · 85 tokens

devops-engineer

CI/CD, deployment, infrastructure specialist. Invoked by /setup-repo and infra tasks.

firatcand/forge · 24 tokens