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.
npx agentmods add skills/nicepkg/ai-workflow/gsc-assistantnpx skills add nicepkg/ai-workflow --skill gsc-assistantgit clone --depth 1 https://github.com/nicepkg/ai-workflowWhat 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 | $0.00075 | $0.01284 |
| Opus 5 | $0.00037 | $0.00642 |
| Sonnet 5 | $0.00015 | $0.00257 |
| Haiku 4.5 | $0.00007 | $0.00128 |
Grade A, and why
gsc-assistant 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 3d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSC Assistant Skill
Purpose
This skill helps manage Google Search Console indexing status by maintaining two markdown tracking files:
-
indexed.md - All indexed pages in two tables:
- "Indexed Public" - URLs confirmed in GSC export data
- "Indexed With Lag" - URLs confirmed via URL Inspection (not yet in export)
-
to-index.md - Pages awaiting indexing:
- Difference between sitemap and total indexed URLs
- Prioritized by categories (configurable)
- Tracks submission dates
When to Use This Skill
- User asks about "indexing status" or "GSC indexing"
- User wants to "compare sitemap with indexed pages"
- User mentions "URL inspection" or "false positives"
- User needs to "track submissions" or "indexing progress"
- User asks to "move indexed pages" or "update indexing status"
- User wants to "generate indexing report"
Key Concepts
GSC Data Lag
Google Search Console export data has approximately 2 weeks lag. Pages that show as indexed in URL Inspection may not appear in the export yet. These are tracked separately as "Indexed With Lag".
False Positives
When checking to-index pages via URL Inspection:
- If indexed: Mark as "false positive - indexed" in Submitted column
- Pre-processing moves these to indexed.md (Indexed With Lag table)
- The "Detected" date is inferred from when the entry was added to to-index
Priority Categories
to-index.md organizes pages by priority:
- Priority 1: High-value content series
- Priority 2: Recent content (current/previous year)
- Priority 3: Specific content collections
- Lower priorities: Archive pages, pagination, etc.
File Schemas
indexed.md
# Indexed Pages
## Indexed Public (GSC Export)
*Last updated: YYYY-MM-DD*
*Source: gsc-export.csv*
| # | URL | Last Crawled |
|---|-----|--------------|
| 1 | https://example.com/page-1/ | 2025-12-01 |
| 2 | https://example.com/page-2/ | 2025-12-02 |
## Indexed With Lag (URL Inspection Confirmed)
*Pages confirmed indexed via URL Inspection but not yet in GSC export*
| # | URL | Detected | Confirmed |
|---|-----|----------|-----------|
| 1 | https://example.com/new-page/ | 12 Dec 2025 | 12 Dec 2025 |
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.
- 3d ago First seen · 192 lines · 75 tokens per session scan A fc6a55cac827
gsc-assistant is a skill published in the GitHub repository nicepkg/ai-workflow (283 stars, last pushed 7mo ago), licensed MIT. It adds 75 tokens to every session and 1,284 once invoked, about $0.0004 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 skills, from other repositories
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
agentic-supply-chain-detection
Detect agentic supply-chain risks: compromised dependencies, malicious plugins/tools/models, and untrusted update sources.
skill-vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
ondb
A logical analysis and reasoning tool for AI. Use when decomposing documents into structured knowledge, querying entities and relations, validating consistency, or indexing files. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", "analyze this document", entity CRUD, or cross-skill…
finding-protocol
Operational-tier finding template — minimal fields for sub-agent decision support. Heavyweight deliverable promotion lives in skills/decepticon/final-report.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…