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.
git clone --depth 1 https://github.com/dork-labs/dorkosWrote 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/dork-labs/dorkos/cleanup)<a href="https://agentmods.dev/commands/dork-labs/dorkos/cleanup"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/cleanup/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/commands/dork-labs/dorkos/cleanup"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/cleanup.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.00014 | $0.02740 |
| Opus 5.5 | $0.00006 | $0.01096 |
| Sonnet 5.5 | $0.00003 | $0.00548 |
| Haiku 4.5 | $0.00001 | $0.00274 |
Grade A, and why
cleanup 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 2mo 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 — 466 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Application Cleanup
Comprehensive codebase maintenance using Knip for dead code detection, combined with linting, type checking, and security auditing.
Arguments
Parse $ARGUMENTS for these options:
Modes (mutually exclusive, default: check)
| Mode | Description |
|---|---|
check |
Report issues only, no changes (default) |
fix |
Auto-fix safe issues (unused imports, exports) |
deep |
Full cleanup with manual review prompts |
Filters (combine with any mode)
| Flag | Effect |
|---|---|
--deps |
Focus on unused dependencies only |
--exports |
Focus on unused exports only |
--files |
Focus on unused files only |
--no-commit |
Skip creating cleanup commit |
Examples
/app:cleanup # Check mode - report all issues
/app:cleanup fix # Auto-fix safe issues
/app:cleanup deep # Full cleanup with prompts
/app:cleanup check --deps # Only check unused dependencies
/app:cleanup fix --exports # Auto-fix unused exports only
Task
Execute phases based on the selected mode.
Phase 1: Pre-Cleanup Validation
Step 1.1: Verify Clean Git State
git status --porcelain
If there are uncommitted changes:
⚠️ You have uncommitted changes. Cleanup works best with a clean working directory.
Use AskUserQuestion:
- Proceed anyway (changes will be mixed with cleanup)
- Stop and let me commit first
Step 1.2: Run Baseline Checks
Ensure the codebase is in a working state before cleanup:
pnpm typecheck
If typecheck fails, stop and report. The codebase must compile before cleanup.
Phase 2: Dead Code Analysis (Knip)
Step 2.1: Run Knip Analysis
pnpm knip 2>&1
Step 2.2: Categorize Issues
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.
- 2mo ago First seen · 466 lines · 14 tokens per session scan A 4d31167ac8cc
cleanup is a command published in the GitHub repository dork-labs/dorkos (12 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 2,740 once invoked, about $0.0001 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 commands, from other repositories
debug-issue
I'm experiencing the following issue: {{1}}.
verify-architecture
Run 64 HOR rules and structural verification on the current codebase.
build-fix
Incrementally fix TypeScript and build errors with minimal diffs. Fix one error at a time for safety.
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
doctor
Diagnose a broken llm-router setup.
relationships
Explore dependencies and relationships for a file or code pattern.