opensource-packager

An open-source project packaging assistant that prepares the files people need to understand, install, use, contribute to, and report issues in a code repository.

In plain words
What is it for?
It analyzes the project and creates or updates files such as CLAUDE.md, setup.sh, README.md, LICENSE, CONTRIBUTING.md, and GitHub issue templates.
Why use it?
It removes the manual work of turning a private or sanitized project into a repository that others can start using. It also gives Claude Code project-specific instructions.

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/sifxprime/kodelyth-ecc/opensource-packager
Clone the repo
git clone --depth 1 https://github.com/sifxprime/kodelyth-ecc
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,757 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.00058 $0.01757
Opus 5 $0.00029 $0.00879
Sonnet 5 $0.00012 $0.00351
Haiku 4.5 $0.00006 $0.00176

Measured 2d ago against content hash 133503decda4, 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 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

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.

# {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
\`\`\`

## Architecture

\`\`\`
{directory tree of key folders with 1-line descriptions}
\`\`\`

{2-3 sentences: what talks to what, data flow}

## Key Files

\`\`\`
{list 5-10 most important files with their purpose}
\`\`\`

## Configuration

All configuration is via environment variables. See \`.env.example\`:

| Variable | Required | Description |
|----------|----------|-------------|
{table from .env.example}

## Contributing

See [CONTRIBUTING.md](CONTRIBUTING.md).

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. 2d ago First seen · 250 lines · 58 tokens per session scan A 133503decda4

Subscribe to this mod's changes

opensource-packager is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 11d ago), licensed MIT. It adds 58 tokens to every session and 1,757 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-30.

Related

Other agents, from other repositories

security-auditor

Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.

addyosmani/agent-skills · 35 tokens

code-reviewer

Reviews code for project guideline compliance, bugs, and quality issues. Use after writing code, before commits, or before PRs. Specify files to review or defaults to unstaged git changes. High-confidence issues only (80+) to minimize noise.

coleam00/Archon · 53 tokens

codemap

Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…

alvinunreal/oh-my-opencode-slim · 0 tokens

design-reviewer

Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…

wasintoh/toh-framework · 85 tokens

qa-sentinel

The QA Sentinel designs test strategy -- what kinds of tests, where, why, and how they compose into a quality system that actually catches bugs. It does not write tests (that is the Testing agent). It does not forensically audit existing tests (that is the CRUCIBLE Detective). It is the architect of quality -- the…

nxtg-ai/forge-plugin · 0 tokens

conversation-analyzer

Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /egc-hookify without arguments.

Jamkris/everything-gemini-code · 30 tokens