opensource-forker

opensource-forker is an agent for Claude Code from raja21068/AutoResearch. It costs 51 tokens per session (1,768 once invoked), scanned A, a copy of opensource-forker, MIT.

A tool for making a private project suitable for public open-source release. It creates a staging copy, removes secrets and generated files, replaces private references, creates an .env.example file, and starts a fresh Git history.

In plain words
What is it for?
Use it to prepare a project for publication by copying selected files, removing credentials, replacing internal domains or paths, documenting configuration values, and cleaning its Git history.
Why use it?
It reduces the manual work and risk involved in publishing internal code. The accompanying report records what was changed during the preparation.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; reads .claude/ paths; mentions CLAUDE.md.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/user/my-api,.

Good fit Use it to prepare a project for publication by copying selected files, removing credentials, replacing internal domains or paths, documenting configuration values, and cleaning its Git history.

Compare 6 agents from other repositories ↓
Install

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.

Made for: Claude Code.

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.

agentmods badge for opensource-forker

README.md
[![agentmods](https://agentmods.dev/badge/agents/raja21068/autoresearch/opensource-forker/github.svg)](https://agentmods.dev/agents/raja21068/autoresearch/opensource-forker)
Your own site
<a href="https://agentmods.dev/agents/raja21068/autoresearch/opensource-forker"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/opensource-forker/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.

agentmods 80×15 button for opensource-forker

Your own site · 80×15
<a href="https://agentmods.dev/agents/raja21068/autoresearch/opensource-forker"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/opensource-forker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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,768 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod 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.1 $0.00051 $0.01768
Opus 5.5 $0.00020 $0.00707
Sonnet 5.5 $0.00010 $0.00354
Haiku 4.5 $0.00005 $0.00177

Measured 1mo ago against content hash 71d6a661a911, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

Origin

This is a copy

86% identical to opensource-forker — 13 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.

skills/agents/opensource-forker.md · 199 lines

How it starts

The opening of the file, as written. The whole thing — 199 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 · 199 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. 1mo ago First seen · 199 lines · 51 tokens per session scan A 71d6a661a911

Subscribe to this mod's changes

opensource-forker is an agent published in the GitHub repository raja21068/AutoResearch (2 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 1,768 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to opensource-forker, differing in 13 lines, and is treated as a copy.

Related

Other agents, from other repositories

debugging-toolkit-dx-optimizer

Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.

wshobson/agents · 44 tokens

vibe-environment-worker

Runs a vibe session's Vercel environment in the target repository for the vibe and handoff orchestrators. Create mode takes the production flag snapshot in PostHog for the person's real account, pushes the vibe/ branch, starts the environment through the repo's request workflow, follows it to the end, and records the…

closedloop-ai/claude-plugins · 217 tokens

Orchestrator-Multi

Multi-agent parallel orchestrator using git worktrees — splits work across N agents, manages territory, merges results.

intellegix/intellegix-code-agent-toolkit · 27 tokens

vibe-seed-pr-worker

Handles the git and GitHub side of a vibe-seed-refresh pull request in the target repository for its orchestrator. Modes: open (push, PR from the template), push (push a fix the orchestrator committed and reply on its review threads), status (one-line PR state), sync (stage a merge of main for the orchestrator to…

closedloop-ai/claude-plugins · 106 tokens

pr-reviewer

Reviews PRs for version bump compliance, KISS/DRY violations, and cross-cutting concerns. Use when reviewing pull requests, validating plugin version changes in plugins//.claude-plugin/plugin.json, or checking files skipped by specialist agents (.githooks, config files, shell scripts, markdown). Triggers on PR review…

closedloop-ai/claude-plugins · 79 tokens

ops-deploy

Secure deployment with pre-deploy checklist. Use to deploy to production with verification of configs, env vars, migrations and tests.

christopherlouet/claude-base · 29 tokens