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.
git clone --depth 1 https://github.com/seyedehsanhadi/sloptrimWrote 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/plugins/seyedehsanhadi/sloptrim/sloptrim)<a href="https://agentmods.dev/plugins/seyedehsanhadi/sloptrim/sloptrim"><img src="https://agentmods.dev/badge/plugins/seyedehsanhadi/sloptrim/sloptrim.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
sloptrim 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "sloptrim",
"version": "0.9.3",
"description": "Scores the first 262,144 characters of extracted prose from files accepted up to 512 KB for plain text and 4 MB for supported archives, against a catalogue of 71 documented patterns, 62 of them with a detector behind them and 50 able to move the score. It names the ones that fired so the flagged spans get fixed before the file ships. The 0 to 100 score lands in one of five bands: clean, light tells, mixed, heavy tells, pervasive tells. Every band describes the prose and none of them names an author. Reads 20 formats including .docx and .epub. Deterministic, Python standard library only, no network, no model. Prose only; code, config and commits stay untouched.",
"author": {
"name": "Seyed Ehsan Hadi",
"url": "https://github.com/seyedehsanhadi"
},
"homepage": "https://github.com/seyedehsanhadi/sloptrim",
"license": "Apache-2.0",
"keywords": [
"humanizer",
"ai-slop",
"de-slop",
"prose",
"prose-linter",
"writing",
"writing-quality",
"text-analysis",
"stylometry",
"markdown",
"docx",
"linter",
"zero-dependency",
"claude-code"
],
"hooks": {
"SessionStart": [
{
"matcher": "startup|resume|clear|compact",
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/sloptrim-activate.js\""
}
]
}
],
"SubagentStart": [
{
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/sloptrim-subagent.js\""
}
]
}
],
"UserPromptSubmit": [
{
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/sloptrim-tracker.js\""
}
]
}
],
"PostToolUse": [
{
"matcher": "Write|Edit|MultiEdit|NotebookEdit|apply_patch",
"hooks": [What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 114 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed 6128ce09b02d
- 8d ago First seen · 72 lines scan A e610e90fbf1d
sloptrim is a plugin published in the GitHub repository seyedehsanhadi/sloptrim (209 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
claude-code-project-boundary
Blocks destructive commands outside the project directory. Allows file operations within the project (refactoring, cleanup) but prevents accidental damage outside it.
cc-notify-hooks
A notification plugin for coding agents such as Claude Code, Codex, DeepSeek Harness, and Reasonix. It sends short waiting updates through several notification channels and handles longer updates asynchronously.
brana
AI development system — skills, agents, and hooks for systematic software engineering with Claude Code.
spec-first marketplace
Spec-first development: define a spec, implement it, and generate docs.
menhera-loop
Menhera-style Claude Code progress messages focused on missing requirements, verification, and hidden TODOs.
skill-engine
Teach Claude your codebase, then keep it taught. On opt-in, clones registered git sources to a local cache (/.cache/skill-engine/) and installs per-skill context files under your project's .claude/skills/. Reads only paths you register.