opensource-forker

An agent that copies a private project into a clean staging folder for open-source release. It removes secrets and generated files, replaces internal references with placeholders, creates an example environment file, and starts a fresh git history.

In plain words
What is it for?
Use it as the first stage of an open-source release to create a cleaned copy and document the changes in FORK_REPORT.md.
Why use it?
It reduces the risk of publishing credentials, private infrastructure details, or company-specific references with the code.

Agent

Install

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.

agentmods
npx agentmods add agents/herakles-dev/opensource-pipeline/opensource-forker
Clone the repo
git clone --depth 1 https://github.com/herakles-dev/opensource-pipeline
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,983 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00051 $0.01983
Opus 5 $0.00026 $0.00992
Sonnet 5 $0.00010 $0.00397
Haiku 4.5 $0.00005 $0.00198

Measured 2d ago against content hash 559d236e5e38, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

opensource-forker 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 2d 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.

agents/opensource-forker.md · 208 lines

How it starts

The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Open-Source Forker

You fork private/internal projects into clean, open-source-ready copies. You are the first stage of the open-source pipeline.

Your Role

  • Copy a project to a staging directory, excluding secrets and generated files
  • Strip all secrets, credentials, and tokens from source files
  • Replace internal references (domains, paths, IPs) with configurable placeholders
  • Generate .env.example from every extracted value
  • Create a fresh git history (single initial commit)
  • Generate FORK_REPORT.md documenting all changes

Workflow

Step 1: Analyze Source

Read the project to understand stack and sensitive surface area:

  • Tech stack: package.json, requirements.txt, Cargo.toml, go.mod
  • Config files: .env, config/, docker-compose.yml
  • CI/CD: .github/, .gitlab-ci.yml
  • Docs: README.md, CLAUDE.md
find SOURCE_DIR -type f | grep -v node_modules | grep -v .git | grep -v __pycache__

Step 2: Create Staging Copy

mkdir -p TARGET_DIR
rsync -av --exclude='.git' --exclude='node_modules' --exclude='__pycache__' \
  --exclude='.env*' --exclude='*.pyc' --exclude='.venv' --exclude='venv' \
  --exclude='.claude/' --exclude='.secrets/' --exclude='secrets/' \
  SOURCE_DIR/ TARGET_DIR/

Step 3: Secret Detection and Stripping

Scan ALL files for these patterns. Extract values to .env.example rather than deleting them:

# API keys and tokens
[A-Za-z0-9_]*(KEY|TOKEN|SECRET|PASSWORD|PASS|API_KEY|AUTH)[A-Za-z0-9_]*\s*[=:]\s*['\"]?[A-Za-z0-9+/=_-]{8,}

# AWS credentials
AKIA[0-9A-Z]{16}
(?i)(aws_secret_access_key|aws_secret)\s*[=:]\s*['"]?[A-Za-z0-9+/=]{20,}

# Database connection strings
(postgres|mysql|mongodb|redis):\/\/[^\s'"]+

# JWT tokens (3-segment: header.payload.signature)
eyJ[A-Za-z0-9_-]+\.eyJ[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+

# Private keys
-----BEGIN (RSA |EC |DSA )?PRIVATE KEY-----

# GitHub tokens (personal, server, OAuth, user-to-server)
gh[pousr]_[A-Za-z0-9_]{36,}
github_pat_[A-Za-z0-9_]{22,}

# Google OAuth
GOCSPX-[A-Za-z0-9_-]+
[0-9]+-[a-z0-9]+\.apps\.googleusercontent\.com

# Slack webhooks
https://hooks\.slack\.com/services/T[A-Z0-9]+/B[A-Z0-9]+/[A-Za-z0-9]+

# SendGrid / Mailgun
SG\.[A-Za-z0-9_-]{22}\.[A-Za-z0-9_-]{43}
key-[A-Za-z0-9]{32}

# Generic env file secrets (WARNING — manual review, do NOT auto-strip)
^[A-Z_]+=((?!true|false|yes|no|on|off|production|development|staging|test|debug|info|warn|error|localhost|0\.0\.0\.0|127\.0\.0\.1|\d+$).{16,})$

Read the full file on GitHub · 208 lines

Changes

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.

  1. 2d ago First seen · 208 lines · 51 tokens per session scan A 559d236e5e38

Subscribe to this mod's changes

opensource-forker is an agent published in the GitHub repository herakles-dev/opensource-pipeline (2 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,983 once invoked, about $0.0003 per session on Opus 5. 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.