github-sensitive-data-cleanup vs Secrets Leak Audit
github-sensitive-data-cleanup is a plugin bundle for AI coding tools published by daymade. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Secrets Leak Audit is an MCP server published by tylerscomic-lab. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  github-sensitive-data-cleanup |  Secrets Leak Audit |
|---|---|---|
| Community marketplace daymade/claude-code-skills | Listed Version: 2.1.0 Forks (GitHub): 229 Stars (GitHub): 1 487 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | github-sensitive-data-cleanup | Secrets Leak Audit |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 487 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 229 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (secrets-leak-audit-mcp.mcpize.run/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/daymade/claude-code-skills | github.com/tylerscomic-lab/secrets-leak-audit-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
github-sensitive-data-cleanup
Scan and remove sensitive data (secrets, API keys, private domains/IPs, PII) from GitHub repository history. Use this skill whenever the user says scan sensitive data, clean git history, remove secrets from repo, sanitize GitHub history, 清理敏感数据, 历史重写, force push, 泄露, or needs to repair a public repo after accidental secret/private context leakage. Also use before any force push to a public repository to verify visibility, backup, and scan results.
Secrets Leak Audit
Scan text and git diffs for committed credentials using real vendor key formats plus entropy.
How to run each
github-sensitive-data-cleanup As a Claude Code plugin
/plugin marketplace add daymade/claude-code-skills
/plugin install github-sensitive-data-cleanup@daymade-skillsSecrets Leak Audit As a remote MCP server
claude mcp add --transport http secrets-leak-audit-mcp https://secrets-leak-audit-mcp.mcpize.run/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Secrets Leak Audit has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: github-sensitive-data-cleanup · What it can do: Secrets Leak Audit · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.