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/cloud99277/kitclaw/skill-admissionnpx skills add cloud99277/KitClaw --skill skill-admissiongit clone --depth 1 https://github.com/cloud99277/KitClawWrote 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/cloud99277/kitclaw/skill-admission)<a href="https://agentmods.dev/skills/cloud99277/kitclaw/skill-admission"><img src="https://agentmods.dev/badge/skills/cloud99277/kitclaw/skill-admission.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.00070 | $0.01202 |
| Opus 5 | $0.00035 | $0.00601 |
| Sonnet 5 | $0.00014 | $0.00240 |
| Haiku 4.5 | $0.00007 | $0.00120 |
Grade A, and why
skill-admission 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 4d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skill-admission — KitClaw Skill 收编验收
检查一个 skill 是否达到 KitClaw 公开仓库的准入标准。
准入标准（7 项检查）
| # | 检查项 | 级别 | 标准 |
|---|---|---|---|
| 1 | lint | 必须 | frontmatter 格式正确，name hyphen-case，description 完整 |
| 2 | security | 必须 | 无 API key、token、password 等敏感数据 |
| 3 | no-personal-deps | 必须 | 无硬编码路径（/home/xxx、/mnt/x）、无用户名引用 |
| 4 | agent-agnostic | 必须 | 不依赖特定 Agent（Claude Code hooks、OMC 等） |
| 5 | self-contained | 必须 | SKILL.md 引用的 scripts/、references/ 文件全部存在 |
| 6 | docs | 推荐 | body ≥5 行，有标题结构，<500 行 |
| 7 | no-aux-files | 推荐 | 无 README.md、CHANGELOG.md、banner 等辅助文件 |
通过规则：所有「必须」项全部 pass → 准入。「推荐」项 fail → 警告但不阻止。
使用
检查单个 skill
python3 ~/.ai-skills/skill-admission/scripts/admit.py ~/.ai-skills/<skill-name>
批量检查（全仓库）
python3 ~/.ai-skills/skill-admission/scripts/admit.py ~/.ai-skills --all
JSON 输出（给 CI/脚本用）
python3 ~/.ai-skills/skill-admission/scripts/admit.py ~/.ai-skills/<skill-name> --format json
Strict 模式（推荐项也当必须）
python3 ~/.ai-skills/skill-admission/scripts/admit.py ~/.ai-skills/<skill-name> --strict
收编流程
1. 运行 admission 检查（原件上跑，不修改原件）
2. 复制到公开仓库（cp -r）
3. 在副本上修复所有 FAIL 项
4. 路径通用化（/home/xxx → $HOME 或通用写法）
5. 删除非标辅助文件（README.md、banner 等）
6. 通过 KitClaw pre-commit hook（自动校验 frontmatter + 安全）
7. git add + commit + push
Frontmatter 校验规则（pre-commit hook）
KitClaw 的 validate_frontmatter.py 对不同文件有不同要求：
| 文件类型 | 必填 (阻塞提交) | 推荐 (warning, 不阻塞) |
|---|---|---|
| SKILL.md | name + description |
tags, scope |
| references/*.md | frontmatter 存在即可 | 无 |
| 其他 .md | title |
tags, scope |
SKILL.md 只需 name + description，与本地 skill 规范一致，不需要额外加 title。
⚠️ 关键规则：不要动原件
公开仓库的 skill 必须从原件复制，绝不能修改 ~/.ai-skills/ 里的源文件。
原因：
~/.ai-skills/是用户私有工作环境，包含个人路径、API key 引用、Agent 专属配置- 公开仓库需要通用化处理（去掉硬编码路径、适配多 Agent），但原件需要保留以便日常使用
- KitClaw 治理 hook 已与本地规范对齐（SKILL.md 只需 name+description），两边标准一致
正确做法：
# 1. 从私有目录复制到公开仓库
cp -r ~/.ai-skills/my-skill ~/projects/kitclaw/core-skills/
# 或
cp -r ~/.ai-skills/my-skill ~/projects/ai-skills-hub/
# 2. 在公开仓库副本上做修改
# - 去掉硬编码路径（/home/xxx → 通用写法）
# - 满足目标仓库的治理标准（如加 title 字段）
# - 删除非标辅助文件（README.md、banner.jpg 等）
# 3. 私有原件保持不动
What ships with it
1 file 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.
- 4d ago First seen · 114 lines · 70 tokens per session scan A a2b391803053
skill-admission is a skill published in the GitHub repository cloud99277/KitClaw (5 stars, last pushed 4mo ago), licensed MIT. It adds 70 tokens to every session and 1,202 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…