What is Trim Reaper?
Trim Reaper is a collection of prompts and a written policy for reducing third-party dependencies with an AI coding agent. It is published in the jmanico/trim-reaper repository, and the README credits Jim Manico of manicode.ai and Manicode Security as its author. The stated aim is to remove dependencies that are unused or easy to replace while keeping libraries that justify themselves through correctness, security or maintenance value.
The content is plain Markdown in a single README. It has four parts: a third-party library policy meant to be copied into a project's AGENTS.md or equivalent agent instructions, an optional assessment-only prompt that inventories dependencies without changing files, a shared instruction that sets the rules for every reduction pass, and eight numbered prompts that go from removing unused packages to a final verification report. A short worked example shows the expected report format and is marked as illustrative rather than a measured result.
There is no application, package, installer or release. The repository holds the README, an AGENTS.md file with maintenance rules for contributors and agents, a scythe logo and the license. According to the commit history, the repository was created on October 21, 2026 with requirements and a design for a command-line tool and an intelligence API, then simplified on October 23, 2026 into the current prompt collection. The most recent commit, on November 8, 2026, set Manicode Security as the copyright holder.
The prompts are written to be agent-neutral and do not assume a particular language, package manager or hosting service. They repeatedly separate removal from replacement: the README points out that replacing a library with local code moves maintenance and security responsibility into the project, and that security-sensitive functions such as cryptography, authentication and complex parsing are expected to stay on established libraries or vetted platform APIs. A pass that cannot be verified is meant to be undone and reported.
Trim Reaper is released under the MIT License, with copyright held by Manicode Security, and commercial use is allowed. The README names two related prompt libraries by the same author, Dread Ledger and Grim Prompter, and notes that manicode.ai sells commercial secure-coding prompts. Other agent add-ons on iThub include the security-audit skill and the Elephant-Goldfish Model plugin.
Key capabilities
- Third-party library policy A ready-made
## Third-party librariessection forAGENTS.mdor similar persistent instructions. It tells the agent to prefer the standard library, platform APIs or existing project functionality, and to add a library only when its benefits outweigh ongoing maintenance, security and upgrade costs. If the project already has dependency guidance, the README asks for the two to be merged into one policy. - Transitive dependency checks Before adding or upgrading a library, the policy requires inspecting the resolved transitive tree, preferring options with fewer transitive dependencies and explaining any substantial increase. Large dependency trees pulled in for functionality the project barely uses are named as something to avoid.
- Package identity verification The policy asks the agent to confirm the exact package name and publisher against the project's own documentation or repository and to check the registry entry live, not to trust registry metadata alone. Package names and versions are never to be taken from model memory, and lookalike names or unexpected ownership changes are to be investigated first.
- Version, license and maintenance rules The agent uses the latest stable release that fits the project and any release-age policy, and treats very recent releases and maintainer changes with caution. License terms of the library and its transitive dependencies are checked against the project's policy, and archived, deprecated or abandoned projects are rejected.
- Security advisory checks with a stop rule Current advisories are checked from official project sources and advisory databases, and the report must name the sources, the date checked, affected versions and applicability. If advisory lookup is unavailable, the agent is told to stop and report that limitation instead of describing an unchecked version as free of vulnerabilities.
- Scoped updates Updates stay within the task: the package manager resolves transitive dependencies, and unrelated upgrades, forced overrides and manual lockfile edits are excluded. Breaking changes are reviewed from release notes before updating, and broader migrations are reported for agreement instead of attempted speculatively.
- Assessment-only prompt An optional first prompt asks the agent to inventory direct and transitive dependencies, find removal, consolidation and replacement candidates and list libraries worth keeping, without modifying files or installing anything. It ends with a prioritized plan and waits for explicit authorization of an implementation scope.
- Shared instruction Pasted once per session before the numbered passes, it requires preserving behavior, error handling, security, public API, downstream compatibility and supported runtimes. The agent establishes a build and test baseline first, works in small reviewable changes, undoes changes that fail verification and must not weaken tests or security controls to make a removal pass.
- Passes 1 and 2: unused packages and the standard library Pass 1 finds and removes confirmed unused dependencies after checking code, dynamic loading, plugins, configuration, scripts, tests and build tooling, treating scanner output only as candidates. Pass 2 replaces dependencies whose used functionality is covered by the language's standard library or supported platform APIs.
- Passes 3 and 4: small replacements and overlap Pass 3 replaces libraries used for simple, narrowly scoped functionality with small local modules and focused tests, deferring anything that turns out to be complex. Pass 4 looks for libraries with overlapping capabilities and standardizes on one the project already requires.
- Passes 5 and 6: transitive overhead and production scope Pass 5 targets dependencies that bring large subtrees for little use and compares the resolved graph before and after. Pass 6 moves development, test and build tools out of production scope and checks the production build from a clean installation, or the packaged artifact in a clean consumer environment for published libraries.
- Pass 7: larger replacements Remaining dependencies are reviewed for bigger rewrites by comparing effort, added code, security and correctness risk, performance and maintenance. Only bounded replacements with a clear net benefit and adequate verification are implemented, and the reasons for keeping the rest are recorded.
- Pass 8: verification and report The final prompt checks a clean reproducible install, build, tests and representative flows, and confirms that manifests, lockfiles, documentation and any SBOM match the final graph. The compact report lists changes, before and after counts with the counting method, exact commands and results, retained dependencies and remaining risks, and forbids invented counts.
- Agent-neutral plain text Every prompt is a fenced text block that can be pasted into Claude Code, Codex or any other coding agent. There is nothing to install, no telemetry and no service; the prompts run with whatever model and permissions the chosen agent already has.
Where Trim Reaper fits
Setting a dependency policy for agent-written code
Projects that use coding agents can paste the library policy into AGENTS.md so that every later session follows the same rules when adding or upgrading packages: verified package identity, transitive tree review, license and advisory checks, and a stop when any of these cannot be verified.
Assessing dependencies before any change
The assessment-only prompt produces an inventory and a prioritized plan without touching files or installing packages. It separates confirmed findings from uncertainties and lists both removal candidates and libraries worth keeping, so the scope of later passes can be authorized explicitly.
Removing unused and redundant packages
Passes 1 and 4 cover packages that are no longer used anywhere and libraries that duplicate each other. The prompts ask the agent to look beyond imports, into dynamic loading, plugins, configuration, scripts and build tooling, before removing anything, and to prune orphaned transitive packages through the package manager.
Replacing small utilities with standard library code
Passes 2 and 3 handle helpers that the language or platform already provides and narrow functions that a short local module can cover. Each replacement comes with tests for the required behavior and edge cases, and anything security-sensitive or unexpectedly complex is left on its existing library.
Shrinking production artifacts
Pass 6 corrects the scope of development, testing and build dependencies so they stay out of production builds, and pass 5 reduces large transitive subtrees. Both compare the dependency graph before and after and verify the production build from a clean installation.
Documenting the result
Pass 8 ends every session with a fixed report format: changes with rationale, measured before and after counts, the exact verification commands and their results, retained dependencies with reasons and remaining risks. Checks that could not run are listed instead of omitted.
Reviews of Trim Reaper
Be the first to share your experience with Trim Reaper.
Write a review
Loading review form…
Found Trim Reaper useful? Upvote it todayYour vote helps other IT teams find it in the daily ranking.

