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/imisic/claude-marketplaceWrote 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/imisic/claude-marketplace/sanitize-public)<a href="https://agentmods.dev/plugins/imisic/claude-marketplace/sanitize-public"><img src="https://agentmods.dev/badge/plugins/imisic/claude-marketplace/sanitize-public/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/plugins/imisic/claude-marketplace/sanitize-public"><img src="https://agentmods.dev/badge/plugins/imisic/claude-marketplace/sanitize-public.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sanitize-public 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 16d 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": "sanitize-public",
"displayName": "Sanitize Public: Leak Check Before Publishing",
"description": "Check a repository, plugin or download for credentials and private details before it goes public. Scans the files and the full Git history, matches your own private names in any spelling, and walks a checklist for leaks a scanner can't see.",
"version": "1.2.2",
"author": {
"name": "Ivan Misic",
"url": "https://ivanmisic.net"
},
"homepage": "https://ivanmisic.net/toolshed/plugins/sanitize-public",
"repository": "https://github.com/imisic/claude-marketplace",
"license": "MIT",
"keywords": [
"secrets",
"secret-scanning",
"privacy",
"leak-detection",
"publishing",
"git-history",
"open-source"
],
"documentationUrl": "https://github.com/imisic/claude-marketplace/tree/main/plugins/sanitize-public#readme",
"privacyPolicyUrl": "https://github.com/imisic/claude-marketplace/tree/main/plugins/sanitize-public#privacy",
"supportUrl": "https://github.com/imisic/claude-marketplace/issues",
"termsOfServiceUrl": "https://github.com/imisic/claude-marketplace/blob/main/LICENSE"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 150 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.
- 16d ago Changed 32425e9f50c7
- 24d ago Changed · +7 lines dd25aeb8c1bc
- 1mo ago First seen · 20 lines scan A 8df7047e5bfa
sanitize-public is a plugin published in the GitHub repository imisic/claude-marketplace (1 stars, last pushed 11d 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
fakoli-crew
Nine specialist AI agents for software engineering — generalist roles (polyglot architect, code reviewer, security auditor, researcher, plugin engineer, integration specialist, documentation writer, infrastructure keeper, QA validator) with TDD enforcement, systematic debugging, and verification gates. Plugin-surface…
fakoli-plugin-critic
Five specialist critic agents for Claude Code plugin development — agent-critic (frontmatter/color/tools), skill-critic (lazy-loading/no-fuzzy-detection), hook-critic (contract-aware/${CLAUDEPLUGINROOT}), mcp-critic (schema/actor-validation), structure-critic (manifest/CHANGELOG/version-sync). Audit any plugin (your.
git-pr-workflows
Git workflow automation, pull request enhancement, and team onboarding processes.
code-refactoring
Code cleanup, refactoring automation, and technical debt management with context restoration.
comprehensive-review
Multi-perspective code analysis covering architecture, security, and best practices.
open-pr
Pre-flight checks and PR creation workflow: run tests, open a PR, code review, and check CI.