OpenGSC: Skill for Claude Code

.agents/skills/site-triage/SKILL.md

site-triage is a skill for Claude Code, Codex from fenjo26/OpenGSC. It costs 45 tokens per session (692 once invoked), scanned A, original, MIT.

A quick technical and Google-search check of a website. It examines security, site health, page-indexing status, search traffic, rankings, and audit issues.

In plain words
What is it for?
Use it to review SSL and safety status, Core Web Vitals, Google index coverage, traffic changes, ranking trends, and affected URLs.
Why use it?
It shows whether a site has urgent problems and helps decide what to fix first before doing deeper search-engine work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is fenjo26/OpenGSC's own configuration. It tells Claude Code and Codex how to work on OpenGSC itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything OpenGSC configures →

Reuse

Borrowing it

Nothing to install: this file belongs to fenjo26/OpenGSC. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/fenjo26/OpenGSC/main/.agents/skills/site-triage/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/fenjo26/OpenGSC

Made for: Claude Code, Codex.

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 site-triage

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/fenjo26/opengsc/site-triage"><img src="https://agentmods.dev/badge/skills/fenjo26/opengsc/site-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 692 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00045 $0.00692
Opus 5 $0.00023 $0.00346
Sonnet 5 $0.00009 $0.00138
Haiku 4.5 $0.00005 $0.00069

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

Security

Grade A, and why

site-triage 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 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.

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.

.agents/skills/site-triage/SKILL.md · 45 lines

How it starts

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

OpenGSC Site Triage

Goal

A fast "is anything on fire?" pass over one site: security/health status, index coverage, and traffic sanity — ending in a short fix-first list. Ideal as the opening move before any deeper SEO work.

Required inputs

  • The site (domain). Call list_sites if unknown.

OpenGSC MCP tools

  • get_alerts: what the app's own hourly alert-cron already fired — rank drops, week-over-week click drops, SSL expiry, low audit scores. Deduplicated per occurrence, so it is an incident list rather than a notification stream. Call this first: it is the instance's own record of what went wrong and when.
  • get_site_health: SSL expiry/grade, Google Safe Browsing verdict, VirusTotal reputation, Core Web Vitals (mobile).
  • get_indexing_status: sitemap URL counts by Google index status + recent URL Inspection results.
  • get_site_audit: the built-in crawler's latest run — health score and issue counts. Pass an issue code to list the affected URLs.
  • get_search_performance: 28-day totals — a traffic collapse shows here first.
  • get_rank_tracker / get_rank_history: tracked keywords trending down are an early warning; the history tells a one-off SERP wobble from a sustained slide.
  • get_clarity: if configured, rage and dead clicks. A page that ranks well but frustrates visitors is a UX incident, not an SEO one.

Workflow

  1. get_alerts (30 days). Anything here already happened — start from the record rather than rediscovering it.
  2. get_site_health. Escalate immediately: expiring/invalid SSL, any Safe Browsing threat, VirusTotal malicious flags. These outrank every SEO consideration.
  3. get_indexing_status. Compare "not indexed"-type counts against the total; list concrete recently-inspected URLs that are excluded.
  4. get_site_audit. A low health score with noindex or broken-link counts explains traffic loss that looks mysterious from GSC alone.
  5. get_search_performance (28 days) — note totals and whether CTR/position look anomalous.
  6. get_rank_tracker if available — flag keywords with position drops, then get_rank_history on the worst to confirm it is a trend.
  7. Rank findings: security > deindexing > crawl/audit errors > vitals > ranking drift.

Read the full file on GitHub · 45 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 · 45 lines · 45 tokens per session scan A 50aa5ef2c633

Subscribe to this mod's changes

site-triage is a skill published in the GitHub repository fenjo26/OpenGSC (22 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 692 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.

Related

Other skills, from other repositories

copilotkit-contribute

Use when contributing to the CopilotKit open-source project — forking, cloning, setting up the monorepo, creating branches, running tests, and submitting pull requests against CopilotKit/CopilotKit.

CopilotKit/CopilotKit · 49 tokens

reskin

Author a NEW skin for the reskinnable-demo app. A skin is a self-contained domain plugin under src/skins/ / that implements the frozen Skin contract (src/shell/skin-contract.ts) to swap the app's entire experience — brand, theme, layout, pages, tools, data, and agent — as a live sales demo. Use when the user says "add…

CopilotKit/CopilotKit · 154 tokens

setup-slack-channel

Use for the PROVIDER half of getting a locally running CopilotKit Channels agent to answer in Slack, when no Slack app exists yet — setting up a Channels bot in Slack for the first time, creating the Slack app and its tokens, attaching it to a managed Intelligence Channel, or when a Channel reports setuprequired, sits…

CopilotKit/CopilotKit · 206 tokens

copilotkit-channels

Use for the CODE half of a managed Intelligence Channel with Slack or Microsoft Teams: customising the Channel a CLI-scaffolded project already ships, or — for a project the CLI did not generate — writing the Channel declaration, the long-running host, and the awaited activation call. Teams provider setup is in scope…

CopilotKit/CopilotKit · 112 tokens

runtime

@copilotkit/runtime — mount a fetch-native CopilotRuntime on any JS server, wire middleware, pick an AgentRunner, instantiate BuiltInAgent (Factory Mode with TanStack AI is the preferred default) or plug in any of 12 external agent frameworks (Mastra, LangGraph, CrewAI Crews/Flows, PydanticAI, ADK, LlamaIndex, Agno…

CopilotKit/CopilotKit · 150 tokens

copilotkit-integrations

Use when wiring an external agent framework (LangGraph, CrewAI, PydanticAI, Mastra, ADK, LlamaIndex, Agno, Strands, Microsoft Agent Framework, or others) into a CopilotKit application via the AG-UI protocol.

CopilotKit/CopilotKit · 61 tokens