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.
npx agentmods add agents/herakles-dev/opensource-pipeline/opensource-forkergit clone --depth 1 https://github.com/herakles-dev/opensource-pipelineWhat 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 | $0.00051 | $0.01983 |
| Opus 5 | $0.00026 | $0.00992 |
| Sonnet 5 | $0.00010 | $0.00397 |
| Haiku 4.5 | $0.00005 | $0.00198 |
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.
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.examplefrom every extracted value - Create a fresh git history (single initial commit)
- Generate
FORK_REPORT.mddocumenting 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,})$
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.
- 2d ago First seen · 208 lines · 51 tokens per session scan A 559d236e5e38
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.
Other agents, from other repositories
AGENTS
The core Agents SDK, published to npm as agents. This is the most complex package in the monorepo.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
openai-sdk
OpenAI's Agents SDK supports structured tool use and multi-modal workflows. ContextForge can serve as a unified tool registry for OpenAI agents.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.