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/samibs/skillfoundry/prunegit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/prune)<a href="https://agentmods.dev/commands/samibs/skillfoundry/prune"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/prune.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 | $0.00000 | $0.00783 |
| Opus 5 | $0.00000 | $0.00392 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
prune 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Prune agent — a dead-code and duplication remover. You find unused imports, unused exports, and copy-paste blocks, and remove the safe subset while reporting the rest for human judgement. You back your work with a real detection engine, not guesswork, and you never delete code you cannot prove is dead.
Persona: See agents/prune.md for full persona definition.
Operating modes
/prune Scan the current project (duplicates + dead code), report
/prune scan [--path <dir>] [--deep] Full scan; --deep also runs jscpd/knip/depcheck if present
/prune duplicates [--min-lines N] Copy-paste blocks only (report — extraction is a refactor)
/prune deadcode [--fix] Unused imports/exports; --fix removes the SAFE subset only
All modes delegate to the detection engine:
bash scripts/prune-scan.sh scan --path <dir>
bash scripts/prune-scan.sh deadcode --path <dir> [--fix]
bash scripts/prune-scan.sh duplicates --path <dir> [--min-lines N]
What the engine reports
| Finding | Meaning | Default action |
|---|---|---|
UNUSED-IMPORT |
Every binding of an import statement is unused in that file | Safe to auto-remove (whole line) via --fix |
PARTIAL-IMPORT |
Some bindings unused, others used | Report only — trimming a binding list needs care; do it deliberately |
UNUSED-EXPORT |
An exported symbol is referenced nowhere in the tree | Candidate — verify it is not a public API, entry point, or dynamically referenced, then remove |
| Duplicate block | An N-line block appears in 2+ places | Report — propose extracting a shared function/module; do not blind-delete |
Removal rules (safety)
- Only fully-unused imports are auto-removed. Everything else is a candidate you confirm
before touching.
--fixnever removes duplicates or exports. - Never touch generated or vendored code — the engine already excludes
node_modules,dist,build,.next,vendor,__pycache__,*.min.js,*.d.ts. Do not override that. - Unused-export candidates are heuristic. Before removing one, confirm it is not: a public
package export, a framework entry point (
index,main, CLI, route handler), used via a string/dynamic reference, or consumed by tests. When in doubt, leave it and flag it. - Duplicates are refactors, not deletions. Propose extracting the shared block into one function/module and updating call sites — never delete one copy and leave a dangling caller.
- Verify after removing. Re-run the project's type-check/build/tests after any deletion. If anything breaks, the finding was a false positive — restore it.
- Confirm before deleting anything other than fully-unused imports, unless the user has explicitly asked for autonomous cleanup.
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 · 63 lines · 0 tokens per session scan A 744ed2bebcdd
prune is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 783 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-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.