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 skills add vincentkoc/dotskills --skill ghcrawl-cluster-operatorgit clone --depth 1 https://github.com/vincentkoc/dotskillsWrote 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/vincentkoc/dotskills/ghcrawl-cluster-operator)<a href="https://agentmods.dev/skills/vincentkoc/dotskills/ghcrawl-cluster-operator"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/ghcrawl-cluster-operator/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/vincentkoc/dotskills/ghcrawl-cluster-operator"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/ghcrawl-cluster-operator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01428 |
| Opus 5 | $0.00023 | $0.00714 |
| Sonnet 5 | $0.00009 | $0.00286 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
ghcrawl-cluster-operator 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 9d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ghcrawl Cluster Operator
Purpose
Operate ghcrawl as a local-first GitHub issue and pull request crawler: inspect the SQLite store, pull GitHub data, refresh summaries and embeddings, build clusters, and extract cluster evidence through deterministic CLI commands.
The default stance is conservative and cost-aware. Inspect first, then run mutating or API-spend commands only when the operator asked for fresh data or enrichment.
When to use
- Inspecting ghcrawl repository state, local runs, thread counts, clusters, or durable cluster decisions.
- Pulling GitHub issue/PR data into a local ghcrawl store.
- Running OpenAI-backed summaries, structured key summaries, embeddings, and clustering.
- Explaining a cluster with members, events, canonical selections, exclusions, and local evidence.
- Operating maintainer edits such as excluding a member from a durable cluster or setting a canonical item.
Workflow
- Start with read-only checks:
doctor,configure,runs,clusters,cluster-explain, andthreads. - Confirm the target repo as
owner/repoand prefer--jsonfor agent-readable output. - Use
syncorrefreshonly when fresh GitHub data is needed. - Use
--include-codeonly when file overlap matters; it hydrates PR file metadata and can increase DB size. - Run structured key summaries before embedding when LLM summaries should influence vectors.
- Run
embed, thencluster, after summary or configuration changes. - Pull one cluster with
cluster-explainbefore making durable maintainer edits. - After durable edits, rerun
clusterand explain the affected cluster to verify the decision stuck.
Inputs
repo(required): GitHub repository inowner/repoformat.db_path(optional): explicit SQLite database path when not using the configured default.cluster_id(optional): durable or run cluster identifier to explain or edit.thread_numbers(optional): comma-separated GitHub issue/PR numbers to inspect.include_code(optional): whether PR file metadata should be hydrated and used as clustering evidence.summary_model(optional): LLM model for structured summaries, usuallygpt-5.4.embedding_basis(optional): vector source such astitle_originalorllm_key_summary.limit(optional): item cap for sync, summaries, or listing commands.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 167 lines · 45 tokens per session scan A 5e79be4dafe9
ghcrawl-cluster-operator is a skill published in the GitHub repository vincentkoc/dotskills (102 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 1,428 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.
Other skills, from other repositories
taiyi-plan
A TaiyiForge planning step that turns a README, product requirements document, or technical plan into a list of separate project changes. Each change includes a suggested work profile, dependencies, and priority.
taiyi-change
A TaiyiForge workflow stage for writing a change proposal in CHANGE.md, with checks for scope, risks, success criteria, and related project documents.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
taiyi-requirement
A requirements-analysis process that turns a proposed change into a REQUIREMENT.md document. It records user needs, acceptance checks, terminology, triggers, and dependencies, with different levels of detail for different project sizes.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.