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 skills/thousandflowers/skillreaper/reapnpx skills add thousandflowers/skillreaper --skill reapgit clone --depth 1 https://github.com/thousandflowers/skillreaperWrote 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/skills/thousandflowers/skillreaper/reap)<a href="https://agentmods.dev/skills/thousandflowers/skillreaper/reap"><img src="https://agentmods.dev/badge/skills/thousandflowers/skillreaper/reap.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.00056 | $0.00534 |
| Opus 5 | $0.00028 | $0.00267 |
| Sonnet 5 | $0.00011 | $0.00107 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
reap 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 6d 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.
What it actually says
skillreaper - context utilization report
Run reap --agent, then paste its output verbatim.
Do not reformat, re-order, summarise, truncate or re-align anything, and do not add a heading or a table of your own: the binary already renders the report, including its closing attribution line.
Arguments
Append any $ARGUMENTS tokens that begin with -; ignore anything else and say
so. --days N sets the evidence window (default 30), --model <id> prices it.
For the full inventory rather than the top rows, use reap --json.
If reap is not installed
Decide with command -v reap and nothing else - never an absolute path, never a
filesystem search: a copy found off PATH may be an older build, and silently
using it hides a broken install.
If that fails, print exactly this and nothing else:
reapis not installed. Run it once without installing anything:npx skillreaperOr install it permanently:
brew install thousandflowers/tap/skillreapergo install github.com/thousandflowers/skillreaper/cmd/reap@latest
If reap is too old
--agent needs reap ≥ 0.5.0. If it exits with
flag provided but not defined: -agent, say the installed build is too old and
give brew upgrade skillreaper (npm: npm install -g skillreaper@latest) - an
upgrade, never the install block above, which they have already done.
Pruning
Never prune on your own initiative. reap prune is interactive and aborts when
it has no terminal, so calling it from here does nothing anyway.
If the user explicitly asks in this turn: get an unambiguous yes, run
reap prune --yes, and remind them of reap restore --all. If the request is
at all ambiguous, hand them the plain reap prune command instead.
For the per-category breakdown, point them at /skillreaper:gap.
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.
- 6d ago First seen · 60 lines · 56 tokens per session scan A 136155785687
reap is a skill published in the GitHub repository thousandflowers/skillreaper (56 stars, last pushed 6d ago), licensed MIT. It adds 56 tokens to every session and 534 once invoked, about $0.0003 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 skills, from other repositories
lithium-kb
Generates, maintains, and visualizes a structured Markdown knowledge base (.lithium-kb/{architecture,debug,tasks,features}) with an interactive Neural Network graph, auto-watch mode, custom agent directives (.agentrules), and MCP server integration for Pi, Claude, Codex, Cursor, and other coding agents. Triggers…
memoryai
Universal autonomous long-term memory for AI agents. Remember everything, send only what matters.
memoryai-capture
Automatically extracts durable knowledge (decisions, preferences, facts, milestones), executes Memory Brain decisions, and handles temporal conflict invalidation.
memoryai-core
Primary master orchestrator for MemoryAI autonomous memory. Automatically detects task context, coordinates specialized sub-skills, enforces token budgets, and manages lifecycle.
memoryai-session
Manages cross-session continuity and first-class session handoffs across Claude Code, Cursor, Codex, Gemini CLI, and MCP.
memoryai-maintainer
Self-improving engineering skill for inspecting MemoryAI codebase quality, diagnosing technical debt, verifying test suites, and performing non-destructive improvements.