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/lftpadilla/agent-dev-kit/knipnpx skills add LFTPadilla/agent-dev-kit --skill knipgit clone --depth 1 https://github.com/LFTPadilla/agent-dev-kitWhat 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.00059 | $0.00448 |
| Opus 5 | $0.00030 | $0.00224 |
| Sonnet 5 | $0.00012 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
knip 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 2d 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
knip — dead code & unused dependency finder
Knip traces the whole project (not one file at a time) to find what nothing references: unused files, exports, types, and dependencies. This is the mechanical version of "delete code you don't need."
Run
npx knip # report unused files, exports, deps, types
npx knip --production # only production code paths (ignore tests/dev)
npx knip --dependencies # just unused/unlisted dependencies
npx knip --fix # auto-remove unused exports/files (review the diff!)
Zero-config for most setups — knip reads package.json + tsconfig.json and
has built-in plugins for Vite, Vitest, Next, ESLint, etc. Add a knip.json
only if entry points are non-standard.
How to use the output
- Run
npx knip. Group findings: unused files / exports / deps / types. - Verify before deleting — knip can flag things reached only by dynamic import, config strings, or framework conventions. Confirm each is truly dead.
- Remove in small commits (files, then exports, then deps). Re-run knip after.
--fixis safe for clearly-unused exports/files, but read the diff — never blind-apply on auth, migration, or public-API code.
Gotchas
- Monorepo: run per-workspace or configure
workspacesinknip.json. - Entry points it can't infer (CLI bins, serverless handlers) → list them in
knip.jsonso it doesn't report them as unused. - Pairs well as a pre-commit gate (warn, don't block) and before any refactor.
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.
- 2d ago First seen · 40 lines · 59 tokens per session scan A 79e778122ca8
knip is a skill published in the GitHub repository LFTPadilla/agent-dev-kit (2 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 448 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.