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.
curl -O https://raw.githubusercontent.com/fenjo26/OpenGSC/main/.agents/skills/site-triage/SKILL.mdgit clone --depth 1 https://github.com/fenjo26/OpenGSCWrote 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/skills/fenjo26/opengsc/site-triage)<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.
<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>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.00045 | $0.00938 |
| Opus 5.5 | $0.00018 | $0.00375 |
| Sonnet 5.5 | $0.00009 | $0.00188 |
| Haiku 4.5 | $0.00005 | $0.00094 |
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 23d 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 — 62 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_sitesif 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 anissuecode 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
get_alerts(30 days). Anything here already happened — start from the record rather than rediscovering it.get_site_health. Escalate immediately: expiring/invalid SSL, any Safe Browsing threat, VirusTotal malicious flags. These outrank every SEO consideration.get_indexing_status. Compare "not indexed"-type counts against the total; list concrete recently-inspected URLs that are excluded.get_site_audit. A low health score withnoindexor broken-link counts explains traffic loss that looks mysterious from GSC alone.get_search_performance(28 days) — note totals and whether CTR/position look anomalous.get_rank_trackerif available — flag keywords with position drops, thenget_rank_historyon the worst to confirm it is a trend.- Rank findings: security > deindexing > crawl/audit errors > vitals > ranking drift.
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.
- 23d ago Changed · +17 lines 41e720ba69d6
- 2mo ago First seen · 45 lines · 45 tokens per session scan A 50aa5ef2c633
site-triage is a skill published in the GitHub repository fenjo26/OpenGSC (51 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 938 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
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…
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…
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
channels-setup
Use when a developer wants to build their first CopilotKit Channels agent and get it answering in Slack or Microsoft Teams: "set up a channel", "connect my agent to Slack", "get my agent into Teams", or starting from nothing and wanting a working channel end to end. Covers the whole path: inspecting or scaffolding the…
intelligence-vocabulary
Locks customer-facing CopilotKit Intelligence docs to one approved name per concept. Use when writing, editing, or reviewing Intelligence docs, nav labels, signup labels, or image alt text in showcase/shell-docs. Don't use for renaming code identifiers, route slugs, env vars, API fields, or component names, or for…
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).