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 This-HW/claude-code-kit --skill using-claude-code-kitgit clone --depth 1 https://github.com/This-HW/claude-code-kitWrote 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/this-hw/claude-code-kit/using-claude-code-kit)<a href="https://agentmods.dev/skills/this-hw/claude-code-kit/using-claude-code-kit"><img src="https://agentmods.dev/badge/skills/this-hw/claude-code-kit/using-claude-code-kit/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/this-hw/claude-code-kit/using-claude-code-kit"><img src="https://agentmods.dev/badge/skills/this-hw/claude-code-kit/using-claude-code-kit.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.00043 | $0.00419 |
| Opus 5.5 | $0.00017 | $0.00168 |
| Sonnet 5.5 | $0.00009 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
using-claude-code-kit 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 1mo 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.
What it actually says
Using claude-code-kit
범용 스킬 규율(스킬 우선 invoke · 합리화 차단 등)은
superpowers:using-superpowers와 공유합니다. superpowers를 함께 쓰면 그 규율을 따르세요 — 여기서 중복 서술하지 않습니다. 아래는 claude-code-kit 전용 추가분입니다.standalone(스킬만 설치, superpowers 없음) 자급 규율: 행동 전, 적용 가능한 스킬이 1%라도 있으면 먼저 invoke한다. 게이트/루프/완료 규율은
rules/가 자동 주입한다 (planning-protocol · loop-engineering · definition-of-done · feedback-loop).
Workflow Chain (kit)
brainstorming → plan-task → auto-dev
- brainstorming — 설계·스펙 (HARD-GATE)
- plan-task — 구조화 계획 (HARD-GATE)
- auto-dev — 구현 + 검증 파이프라인
완료 선언 전
scripts/verify-done.sh게이트 통과 필수 (definition-of-done).
Work System Detection
docs/works/ 폴더가 있으면: Work ID 기반 추적 활성화
없으면: 파일 없이 파이프라인만 실행 (fallback mode)
이 스킬 밖에 있는 것
- 비신뢰 텍스트 취급 →
rules/untrusted-text.md(core 규범, 상시 주입) - 메모리 MCP·superpowers interop → 해당 도구가 있을 때만. 킷은 존재를 가정하지 않는다
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.
- 1mo ago Changed · -75 lines 2ce979a8f06c
- 1mo ago First seen · 112 lines · 43 tokens per session scan A ce972b31d529
using-claude-code-kit is a skill published in the GitHub repository This-HW/claude-code-kit (4 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 419 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-31.
Other skills, from other repositories
code-standards
Prabhdeep (Sonu) Singh's personal coding standards — the house rules and quality bar for how code gets written. INVOKE before writing, generating, refactoring, or reviewing ANY code in ANY language — schemas, endpoints, queries, logging, validation, error handling — even when nobody says "standards" or "style".…
design-tree
Make design decisions as an explicit branching tree — genuine alternatives, decisive rationale, rejected branches preserved. INVOKE PROACTIVELY when planning or designing any implementation approach, or choosing between architectures, libraries, or data models — especially in plan mode. Skip trivial or forced changes…
self-review
Surface the riskiest parts of the current diff so a reviewer knows where to look hardest — one inline pass on small diffs, one cold read on a cheaper model tier with in-session synthesis on substantial ones. INVOKE PROACTIVELY whenever a change is finished and about to be handed off, reviewed, or shipped. It points…
ticket-lifecycle
The ticket-as-control-plane rulebook — the single home for the tracker-operations contract, tracker resolution, the type/priority taxonomy, human-only trigger authorization, derived status, and trust boundaries. INVOKE when reading or writing tickets in a queue-driven flow, resolving a repo's tracker, or deciding…
tdd
Test-driven development — the red-green-refactor discipline for code that's correct by design, not by accident. INVOKE PROACTIVELY whenever writing or changing code, fixing a bug, adding or structuring tests, or choosing what to mock — even when nobody says "TDD" or "tests". (Tests are code held to…
pr-conventions
Author PR descriptions from the right per-change-type template (the repo's own PULLREQUESTTEMPLATE wins), embed issue-tracker links, keep the description current as fixes land, and reply to human and bot review threads. INVOKE when opening or updating a PR or responding to reviewer comments — inside /sonu:ship or…