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/oyusypenko/creoWrote 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/oyusypenko/creo/creo-gsc)<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.
<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>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.02550 |
| Opus 5 | $0.00026 | $0.01275 |
| Sonnet 5 | $0.00010 | $0.00510 |
| Haiku 4.5 | $0.00005 | $0.00255 |
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 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
- Always activate the venv/PYTHONPATH before running commands.
- For
full-seoanalysis, the command runs all 9 analyzers automatically. - For
site-audit, suggest reasonable limits:--max-pages 100for quick audits,--max-pages 500for thorough ones. - If a GSC API command fails with auth errors, inform the user they need to configure a Google service account.
- Present results clearly. Highlight critical issues first, then warnings, then recommendations.
- 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
- A single page analysis: use
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.
- 10d ago First seen · 231 lines · 51 tokens per session scan A eb8d77842d82
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.
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…
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
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…
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.
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…
devops-engineer
CI/CD, deployment, infrastructure specialist. Invoked by /setup-repo and infra tasks.