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.
/plugin marketplace add andrewm4894/claude-log-cleanernpx agentmods add plugins/andrewm4894/claude-log-cleaner/log-cleanergit clone --depth 1 https://github.com/andrewm4894/claude-log-cleanerWrote 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/andrewm4894/claude-log-cleaner/log-cleaner)<a href="https://agentmods.dev/plugins/andrewm4894/claude-log-cleaner/log-cleaner"><img src="https://agentmods.dev/badge/plugins/andrewm4894/claude-log-cleaner/log-cleaner.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
log-cleaner 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
{
"name": "log-cleaner",
"description": "Automatically delete Claude Code session logs after a configurable retention period to prevent sensitive data exposure",
"version": "2.8.0",
"author": {
"name": "andrewm4894"
},
"homepage": "https://github.com/andrewm4894/claude-log-cleaner",
"repository": "https://github.com/andrewm4894/claude-log-cleaner",
"license": "MIT",
"keywords": [
"security",
"cleanup",
"logs",
"privacy",
"secrets"
]
}
What it installs
The manifest is a name and a version. 4 commands, 1 hook travel with it, and installing the plugin installs all of them — 44 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 19 lines scan A add9b04c4f96
log-cleaner is a plugin published in the GitHub repository andrewm4894/claude-log-cleaner (4 stars, last pushed 7mo ago), licensed MIT. 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-31.
Other plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.
knowledge-work-plugins marketplace
Plugin marketplace listing 98 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
container
Teaches Claude container's command surface and how it maps to Docker, Lima, Colima, and Podman on macOS.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.