knip

A command for finding unused files, packages, exports, and types in JavaScript or TypeScript projects, using the knip tool. An export is code made available to other files, while a dependency is a package the project uses.

In plain words
What is it for?
Use it to scan a project, review unused dependencies or exports, find unused files, inspect configuration, or guide cleanup.
Why use it?
It helps locate dead code and unused packages that make a project harder to maintain and can obscure what the application actually needs.

Command

Install

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.

agentmods
npx agentmods add commands/iwritec0de/app-dev/knip
Clone the repo
git clone --depth 1 https://github.com/iwritec0de/app-dev
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,087 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.02087
Opus 5 $0.00008 $0.01043
Sonnet 5 $0.00003 $0.00417
Haiku 4.5 $0.00002 $0.00209

Measured yesterday against content hash 91d092de7099, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

commands/knip.md · 274 lines

How it starts

The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Knip — Dead Code Cleanup

Find and remove unused code, dependencies, exports, and files in JavaScript/TypeScript projects.

Load the knip-cleanup skill for configuration patterns, safe removal workflows, and false positive handling.

Usage

/knip [scan|fix|deps|exports|files|config|init]

Arguments

Parse $ARGUMENTS to extract the subcommand:

  • scan (default) — Full scan with categorized report
  • fix — Interactive guided cleanup with auto-fix
  • deps — Focus on unused and unlisted dependencies
  • exports — Focus on unused exports and types
  • files — Focus on unused files
  • config — Show current knip configuration and detected plugins
  • init — Set up knip in the project with recommended config

Instructions

Pre-flight Check

Before any subcommand, verify knip is available:

  1. Check package.json for knip in devDependencies.
  2. If not installed, ask the user if they'd like to install it:
    pnpm add -D knip
    
  3. Detect the project type (Next.js, Vite, Express, etc.) from package.json and config files — this informs which knip plugins will activate automatically.

/knip scan

Run a full knip analysis and present a categorized report:

  1. Run knip with JSON output for parsing:

    pnpm knip --reporter json 2>/dev/null
    
  2. If knip exits with findings, also run compact output for the user:

    pnpm knip --reporter compact
    
  3. Present results as a summary table:

    ## Knip Scan Results
    
    | Category | Count | Severity |
    |----------|-------|----------|
    | Unlisted dependencies | X | CRITICAL |
    | Unresolved imports | X | CRITICAL |
    | Unused dependencies | X | HIGH |
    | Unused devDependencies | X | MEDIUM |
    | Unused files | X | MEDIUM |
    | Unused exports | X | LOW |
    | Unused types | X | LOW |
    | Duplicate packages | X | INFO |
    
  4. Below the summary, list specifics for CRITICAL and HIGH items with file paths.

  5. Suggest next steps:

    • If unlisted deps found: "Run /knip deps to fix dependency issues first"
    • If unused deps found: "Run /knip fix for guided cleanup"
    • If only unused exports/types: "Run /knip exports to review"

Read the full file on GitHub · 274 lines

Changes

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.

  1. yesterday First seen · 274 lines · 16 tokens per session scan A 91d092de7099

Subscribe to this mod's changes

knip is a command published in the GitHub repository iwritec0de/app-dev (3 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 2,087 once invoked, about $0.0001 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.