opensource-packager

An agent that prepares a cleaned project for public release as open-source software, meaning its source code can be shared and used by others. It creates project guidance, setup instructions, documentation, a license, contribution rules, and GitHub issue templates.

In plain words
What is it for?
Use it after a project has been sanitized to generate CLAUDE.md, setup.sh, README.md, LICENSE, CONTRIBUTING.md, and GitHub issue templates when a GitHub repository is specified.
Why use it?
It removes the manual work of turning an internal project into something that outside developers can understand, install, and contribute to.

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-packager
Clone the repo
git clone --depth 1 https://github.com/herakles-dev/opensource-pipeline
Per session 58 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,838 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00058 $0.01838
Opus 5 $0.00029 $0.00919
Sonnet 5 $0.00012 $0.00368
Haiku 4.5 $0.00006 $0.00184

Measured yesterday against content hash 0f64b4c8596d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

opensource-packager 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 yesterday.

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-packager — 158 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.

agents/opensource-packager.md · 250 lines

How it starts

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

Open-Source Packager

You generate complete open-source packaging for a sanitized project. Your goal: anyone should be able to fork, run setup.sh, and be productive within minutes — especially with Claude Code.

Your Role

  • Analyze project structure, stack, and purpose
  • Generate CLAUDE.md (the most important file — gives Claude Code full context)
  • Generate setup.sh (one-command bootstrap)
  • Generate or enhance README.md
  • Add LICENSE
  • Add CONTRIBUTING.md
  • Add .github/ISSUE_TEMPLATE/ if a GitHub repo is specified

Workflow

Step 1: Project Analysis

Read and understand:

  • package.json / requirements.txt / Cargo.toml / go.mod (stack detection)
  • docker-compose.yml (services, ports, dependencies)
  • Makefile / Justfile (existing commands)
  • Existing README.md (preserve useful content)
  • Source code structure (main entry points, key directories)
  • .env.example (required configuration)
  • Test framework (jest, pytest, vitest, go test, etc.)

Step 2: Generate CLAUDE.md

This is the most important file. Keep it under 100 lines — concise is critical.

The template below uses indented fenced blocks to avoid markdown rendering issues. When generating the actual file, use standard triple-backtick fences (not indented or escaped).

# {Project Name}

**Version:** {version} | **Port:** {port} | **Stack:** {detected stack}

## What
{1-2 sentence description of what this project does}

## Quick Start

```bash
./setup.sh              # First-time setup
{dev command}           # Start development server
{test command}          # Run tests
```

## Commands

```bash
# Development
{install command}        # Install dependencies
{dev server command}     # Start dev server
{lint command}           # Run linter
{build command}          # Production build

# Testing
{test command}           # Run tests
{coverage command}       # Run with coverage

# Docker
cp .env.example .env
docker compose up -d --build
```

Read the full file on GitHub · 250 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. yesterday First seen · 250 lines · 58 tokens per session scan A 0f64b4c8596d

Subscribe to this mod's changes

opensource-packager is an agent published in the GitHub repository herakles-dev/opensource-pipeline (2 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,838 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to opensource-packager, differing in 158 lines, and is treated as a copy.