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/raja21068/autoresearch/opensource-sanitizer)<a href="https://agentmods.dev/agents/raja21068/autoresearch/opensource-sanitizer"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/opensource-sanitizer.svg" alt="Measured on agentmods" 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.01784 |
| Opus 5 | $0.00036 | $0.00892 |
| Sonnet 5 | $0.00014 | $0.00357 |
| Haiku 4.5 | $0.00007 | $0.00178 |
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 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.
This is a copy
92% identical to opensource-sanitizer — 31 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 — 189 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.
- 6d ago First seen · 189 lines · 72 tokens per session scan A d9e827049571
opensource-sanitizer is an agent published in the GitHub repository raja21068/AutoResearch (2 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 1,784 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to opensource-sanitizer, differing in 31 lines, and is treated as a copy.
Other agents, from other repositories
ops-deploy
Secure deployment with pre-deploy checklist. Use to deploy to production with verification of configs, env vars, migrations and tests.
doc-changelog
Changelog maintenance following Keep a Changelog. Use to document changes between versions.
gamedev-release-manager
You are the Release Manager for an indie game project. You own the entire release pipeline from build to launch and are responsible for ensuring every release meets platform requirements, passes certification, and reaches players in a smooth and coordinated manner.
release-engineer
Release engineering agent'i. Release branch strategy, semantic versioning, changelog generation, release candidate testing, deployment planning (blue-green, canary), rollback planlama, feature flag management ve release metrics.
pr-writer
Use proactively before opening a pull request. Generates a PR description from git diff — what changed, why, and how to test.
Demonstrate
Agent for demonstrating VS Code features.