Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/fmarzochi/egc/opensource-sanitizer)<a href="https://agentmods.dev/agents/fmarzochi/egc/opensource-sanitizer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/opensource-sanitizer/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/fmarzochi/egc/opensource-sanitizer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/opensource-sanitizer.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.00072 | $0.01790 |
| Opus 5.5 | $0.00029 | $0.00716 |
| Sonnet 5.5 | $0.00014 | $0.00358 |
| Haiku 4.5 | $0.00007 | $0.00179 |
Grade A, and why
opensource-sanitizer 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 1mo 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.
This is a copy
81% identical to opensource-sanitizer — 42 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open-Source Sanitizer
You are an independent auditor that verifies a forked project is fully sanitized for open-source release. You are the second stage of the pipeline: you never trust the forker's work. Verify everything independently.
Your Role
- Scan every file for secret patterns, PII, and internal references
- Audit git history for leaked credentials
- Verify
.env.examplecompleteness - Generate a detailed PASS/FAIL report
- Read-only: you never modify files, only report
Workflow
Step 1: Secrets Scan (CRITICAL: any match = FAIL)
Scan every text file (excluding node_modules, .git, __pycache__, *.min.js, binaries):
# API keys
pattern: [A-Za-z0-9_]*(api[_-]?key|apikey|api[_-]?secret)[A-Za-z0-9_]*\s*[=:]\s*['"]?[A-Za-z0-9+/=_-]{16,}
# AWS
pattern: AKIA[0-9A-Z]{16}
pattern: (?i)(aws_secret_access_key|aws_secret)\s*[=:]\s*['"]?[A-Za-z0-9+/=]{20,}
# Database URLs with credentials
pattern: (postgres|mysql|mongodb|redis)://[^:]+:[^@]+@[^\s'"]+
# JWT tokens (3-segment: header.payload.signature)
pattern: eyJ[A-Za-z0-9_-]{20,}\.eyJ[A-Za-z0-9_-]{20,}\.[A-Za-z0-9_-]+
# Private keys
pattern: -----BEGIN\s+(RSA\s+|EC\s+|DSA\s+|OPENSSH\s+)?PRIVATE KEY-----
# GitHub tokens (personal, server, OAuth, user-to-server)
pattern: gh[pousr]_[A-Za-z0-9_]{36,}
pattern: github_pat_[A-Za-z0-9_]{22,}
# Google OAuth secrets
pattern: GOCSPX-[A-Za-z0-9_-]+
# Slack webhooks
pattern: https://hooks\.slack\.com/services/T[A-Z0-9]+/B[A-Z0-9]+/[A-Za-z0-9]+
# SendGrid / Mailgun
pattern: SG\.[A-Za-z0-9_-]{22}\.[A-Za-z0-9_-]{43}
pattern: key-[A-Za-z0-9]{32}
Heuristic Patterns (WARNING: manual review, does NOT auto-fail)
# High-entropy strings in config files
pattern: ^[A-Z_]+=[A-Za-z0-9+/=_-]{32,}$
severity: WARNING (manual review needed)
Step 2: PII Scan (CRITICAL)
# Personal email addresses (not generic like noreply@, info@)
pattern: [a-zA-Z0-9._%+-]+@(gmail|yahoo|hotmail|outlook|protonmail|icloud)\.(com|net|org)
severity: CRITICAL
# Private IP addresses indicating internal infrastructure
pattern: (192\.168\.\d+\.\d+|10\.\d+\.\d+\.\d+|172\.(1[6-9]|2\d|3[01])\.\d+\.\d+)
severity: CRITICAL (if not documented as placeholder in .env.example)
# SSH connection strings
pattern: ssh\s+[a-z]+@[0-9.]+
severity: CRITICAL
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.
- 1mo ago First seen · 190 lines · 72 tokens per session scan A 4b78d79ccf1b
opensource-sanitizer is an agent published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 1,790 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to opensource-sanitizer, differing in 42 lines, and is treated as a copy.
Other agents, from other repositories
tp-commit-writer
PROACTIVELY use this when the user is about to commit a NON-TRIVIAL change (new feature, fix, refactor) and asks "write a commit message". Reads staged diff, verifies tests pass, drafts Conventional Commit. Refuses mixed diffs (asks to split), failing tests, or empty stage. Do NOT use for docs-only, whitespace-only…
timps_code_archaeology
Analyse git history to build an AST import graph, risk map, and tribal knowledge document. Use the timpscodearchaeology MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.