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/vincentkoc/dotskills/crawlkitnpx skills add vincentkoc/dotskills --skill crawlkitgit 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/crawlkit)<a href="https://agentmods.dev/skills/vincentkoc/dotskills/crawlkit"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/crawlkit.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.00652 |
| Opus 5 | $0.00015 | $0.00326 |
| Sonnet 5 | $0.00006 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
crawlkit 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 5d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crawlkit
Purpose
Maintain crawlkit, the shared Go library for crawl app archive infrastructure. Use this skill to keep shared archive infrastructure reusable, tagged, and safe for downstream app branches.
When to use
- Editing or reviewing
crawlkit. - Moving common crawl app behavior into the library.
- Checking whether
gitcrawl,slacrawl,discrawl, ornotcrawlcan merge against a releasedcrawlkittag. - Preparing or verifying a
crawlkitGo module release. - Investigating shared TUI, snapshot, config, SQLite, mirror, progress, or control metadata behavior.
Workflow
-
Locate the
crawlkitcheckout from the current repository, an explicit user path, or the configured workspace root. -
Read repo-local
AGENTS.md,README.md,CONTRIBUTING.md, anddocs/publishing.mdbefore release or compatibility work. -
Keep provider-specific logic out of
crawlkit. Shared mechanics belong in packages such asconfig,store,snapshot,mirror,state,output,progress,tui,cache, andcontrol. -
Run the library gate with workspace masking disabled:
GOWORK=off go mod tidy git diff --exit-code -- go.mod go.sum GOWORK=off go vet ./... GOWORK=off go test -count=1 ./... -
For release checks, verify the signed tag and public Go proxy:
git tag -v <version> GOPROXY=https://proxy.golang.org GONOSUMDB= go list -m github.com/vincentkoc/crawlkit@<version> -
For downstream readiness, inspect app branches read-only. Confirm they are clean, rebased, require the released
crawlkitversion, and pass:GOWORK=off go test ./... <app> --help <app> --version <app> metadata --json <app> status --json <app> tui --json -
Use temp
HOME,XDG_CONFIG_HOME, andXDG_CACHE_HOMEfor CLI smokes. Never mutate live app archives.
Inputs
- Target task: library edit, release verification, downstream readiness, or TUI backport.
- Optional version tag such as
v0.4.0. - Optional downstream app branch paths.
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.
- 5d ago First seen · 80 lines · 30 tokens per session scan A 3f055092a59f
crawlkit is a skill published in the GitHub repository vincentkoc/dotskills (102 stars, last pushed 13d ago), licensed MIT. It adds 30 tokens to every session and 652 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
ship
Commit and push the current work properly — lint, run the release gate, write a detailed commit message, push to GitHub. Use whenever work reaches a milestone or the user says ship it, commit, or push.
nextclaw-npm-release
NextClaw NPM package 与 runtime channel 发布的专项流程 owner；用于发布 NPM、NPM 测试版、NextClaw 常规正式版及其恢复，覆盖 beta/stable、真实安装和分支回流，并按当前阶段读取一个 reference。.
development-delivery
通用开发生命周期的「交付、发布与部署」阶段 owner；当结果已经达到交付条件，或用户明确要求提交、发布、部署时使用，负责授权边界、结果交接和专项发布路由，不负责实现或 Review。.
nextclaw-desktop-release
NextClaw Desktop 构建、发布、恢复与运行冒烟流程 owner。.
pre-release-check
The final gate before a release is cut — go green, reconcile the release PR against what actually landed, sweep what CI can't see, check the roadmap and ADR statuses, optionally deep-review, then return a ship-or-hold verdict.
nextclaw-release-notes
当用户要求提交、收尾、changelog、release notes、版本更新笔记或发布变更汇总时使用；先选择提交范围判断、版本笔记、配图/社交一个阶段并读取对应 reference。.