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/herakles-dev/opensource-pipeline/opensource-packager)<a href="https://agentmods.dev/agents/herakles-dev/opensource-pipeline/opensource-packager"><img src="https://agentmods.dev/badge/agents/herakles-dev/opensource-pipeline/opensource-packager/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.
<a href="https://agentmods.dev/agents/herakles-dev/opensource-pipeline/opensource-packager"><img src="https://agentmods.dev/badge/agents/herakles-dev/opensource-pipeline/opensource-packager.svg" alt="Reviewed on agentmods" width="80" 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.00058 | $0.01838 |
| Opus 5.5 | $0.00023 | $0.00735 |
| Sonnet 5.5 | $0.00012 | $0.00368 |
| Haiku 4.5 | $0.00006 | $0.00184 |
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 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.
This is a copy
81% identical to opensource-packager — 171 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 — 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
```
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.
- 1mo ago First seen · 250 lines · 58 tokens per session scan A 0f64b4c8596d
opensource-packager is an agent published in the GitHub repository herakles-dev/opensource-pipeline (2 stars, last pushed 29d ago), licensed MIT. It adds 58 tokens to every session and 1,838 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to opensource-packager, differing in 171 lines, and is treated as a copy.
Other agents, from other repositories
github-issue-sync-worker
Atomic GitHub issue synchronization executor. Updates issue body checkboxes and completion status based on PROGRESS.json changes.
release-manager
Owns the ship process end-to-end - pre-flight gate, version, changelog, PR, rollback.
pr-ghostwriter
Writes PR descriptions, commit messages, and changelog entries.
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-readiness-reviewer
Use when you need to give go/no-go verdicts for demo, handoff, deployment, or release without editing.
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.