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 commands/insight-services-apac/ingenious/knipgit clone --depth 1 https://github.com/Insight-Services-APAC/ingeniousWrote 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/commands/insight-services-apac/ingenious/knip)<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/knip"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/knip.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.1 | $0.00000 | $0.00530 |
| Opus 5 | $0.00000 | $0.00265 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find and Remove Dead Code with Knip
Use Knip to analyze the codebase for unused exports, dependencies, and dead code.
1. Install Knip (if missing)
npm install -D knip
2. Run Dead Code Analysis
npx knip
For more verbose output:
npx knip --include files,exports,types,duplicates
3. What Knip Detects
- Unused files - Files not imported anywhere
- Unused exports - Exported functions/classes/variables not imported
- Unused dependencies - Packages in package.json not used in code
- Unused devDependencies - Dev packages not referenced
- Unlisted dependencies - Used but not in package.json
- Duplicate exports - Same thing exported multiple times
4. Verify Each Finding
For each item detected:
-
Cross-check references across the codebase:
- Dynamic imports:
import(),require() - String-based access:
components[name] - Vue template references
- Config file references
- Test file usage
- Dynamic imports:
-
Check for indirect usage:
- Entry points in build config
- Plugin registrations
- Global component registration
- Runtime computed property access
5. Remove Verified Dead Code
If certain the code is unused:
# Remove unused dependency
npm uninstall <package-name>
# Or remove unused file/export manually
6. Test After Each Removal
npm run build:check
npm test
7. Commit Incrementally
git add .
git commit -m "chore(cleanup): remove unused <item> as detected by knip"
8. Configure Knip
Create knip.json to customize (adjust paths to match project structure):
{
"entry": ["src/**/*.ts", "**/*.config.{js,ts}"],
"project": ["src/**/*.{ts,tsx,js,jsx,vue}"],
"ignore": ["**/*.d.ts", "**/test/**", "**/node_modules/**", "**/.venv/**"],
"ignoreDependencies": ["@types/*"]
}
9. Final Validation
npx knip
npm run build
npm test
Goal: Zero unused exports, files, or dependencies reported by Knip.
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.
- yesterday First seen · 94 lines · 0 tokens per session scan A d5a8609b7382
knip is a command published in the GitHub repository Insight-Services-APAC/ingenious (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 530 tokens. 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-09-04.
Other commands, from other repositories
manps
Inspect project health through mancode.
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
cleanup
Run a systematic cleanup on the provided code to resolve smells, simplify complexity, and enforce best practices.
flutter-build
Fix Dart analyzer errors and Flutter build failures incrementally. Invokes the dart-build-resolver agent for minimal, surgical fixes.
lint
Run lint + format + type checks and report results (do not auto-fix unless I ask).
debug-method
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions.