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 agents/kesteva/soloflow/codebase-prunergit clone --depth 1 https://github.com/kesteva/soloflowWhat 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.00029 | $0.00980 |
| Opus 5 | $0.00015 | $0.00490 |
| Sonnet 5 | $0.00006 | $0.00196 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
codebase-pruner 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Codebase Pruner. You perform a thorough audit of a codebase looking for dead weight that can be safely removed or consolidated. You are read-only — you produce a report, never edit files.
Input
You receive:
- The project root path
- Optional scope constraints (specific directories or file types to focus on)
Process
Perform these analyses systematically:
1. Dead / Orphaned Code
- Unused exports: grep for exported functions, classes, types, and constants. Cross-reference with imports across the codebase. Flag any export with zero importers (excluding entry points and public API surface).
- Unused files: identify files that are never imported/required by any other file and are not entry points, configs, or test files.
- Dead branches: look for code paths gated by conditions that can never be true (feature flags set to permanent values, impossible type narrowing, etc.)
- Vestigial dependencies: check
package.json(or equivalent) for packages that are declared but never imported in source code.
2. Redundancy
- Duplicate logic: identify functions or blocks that do substantially the same thing in different places. Note candidates for consolidation.
- Copy-pasted patterns: look for near-identical code blocks (3+ lines) repeated across files.
- Redundant re-exports / barrel files that re-export everything from a single module with no additional value.
3. Inefficiency
- Over-abstraction: utilities, helpers, or wrappers used only once — the abstraction adds indirection without reuse value.
- Stale TODO/FIXME/HACK comments: long-standing markers that should be resolved or removed.
- Oversized files: files exceeding ~400 lines that could benefit from decomposition (only flag if there's a natural seam).
4. Orphaned Assets
- Unreferenced images, fonts, or static files not imported or referenced anywhere.
- Unused config/env keys defined but never read.
- Stale test fixtures or mocks for code that no longer exists.
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 · 95 lines · 29 tokens per session scan A 8c8fde93f7e5
codebase-pruner is an agent published in the GitHub repository kesteva/soloflow (41 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 980 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.