Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add nikshepsvn/scrim/plugin install scrimWrote 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/agents/nikshepsvn/scrim/scrim-retrieve)<a href="https://agentmods.dev/agents/nikshepsvn/scrim/scrim-retrieve"><img src="https://agentmods.dev/badge/agents/nikshepsvn/scrim/scrim-retrieve/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/agents/nikshepsvn/scrim/scrim-retrieve"><img src="https://agentmods.dev/badge/agents/nikshepsvn/scrim/scrim-retrieve.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.00051 | $0.00179 |
| Opus 5 | $0.00026 | $0.00089 |
| Sonnet 5 | $0.00010 | $0.00036 |
| Haiku 4.5 | $0.00005 | $0.00018 |
Grade A, and why
scrim-retrieve 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 10d 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
You retrieve omitted tool output. You do not analyze the whole session.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/scrim.py" get <id>
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/scrim.py" get <id> 118-130
If the user did not give a line range and the file is large, fetch 1-80 first and say how to ask for more. Never paste more than ~200 lines back to the parent unless they insist.
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.
- 10d ago First seen · 17 lines · 0 tokens per session scan A 15a64e78e998
scrim-retrieve is an agent published in the GitHub repository nikshepsvn/scrim (4 stars, last pushed 22d ago), licensed MIT. It adds 51 tokens to every session and 179 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-31.
Other agents, from other repositories
change-cartographer
An agent that maps a code patch: which parts changed, what each change is meant to do, and how the changed parts depend on one another.
logic-tracer
An agent that explains how a code change alters what a program does while it runs, including how data moves through the code before and after the change.
arn-code-ux-specialist
This agent should be used when the user needs UI/UX design guidance for a feature, or when the arn-code-feature-spec-teams skill needs a UX specialist perspective during team debate. Specializes in component architecture, user experience flows, accessibility, and frontend patterns. Context: Invoked by…
backend
Backend development expert for API design review, business logic analysis, error handling assessment, and performance evaluation. Use when reviewing server-side code, API endpoints, data processing, or service integrations.
coverage-guardian
Use to verify and repair the coverage gate — run the repo's unit tests with coverage, find touched files below 95%, and write the specific missing tests to close the gaps. Language- and framework-agnostic.
requirements-reviewer
Reviews a draft requirements.md against the conversation history and glean scratch files. Detects coverage gaps (missing user-stated requirements), hallucinations (ACs without conversational source), and quality issues (EARS structure, CONFIRMED/ASSUMPTION labels, scope clarity, Out of Scope adequacy). Triggered…