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/sifxprime/kodelyth-ecc/opensource-packager)<a href="https://agentmods.dev/agents/sifxprime/kodelyth-ecc/opensource-packager"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/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/sifxprime/kodelyth-ecc/opensource-packager"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/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.01757 |
| Opus 5.5 | $0.00023 | $0.00703 |
| Sonnet 5.5 | $0.00012 | $0.00351 |
| Haiku 4.5 | $0.00006 | $0.00176 |
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
89% identical to opensource-packager — 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.
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).
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 133503decda4
opensource-packager is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 17d ago), licensed MIT. It adds 58 tokens to every session and 1,757 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to opensource-packager, differing in 13 lines, and is treated as a copy.
Other agents, from other repositories
git-manager
Manage version control and Git operations.
release-summarizer
Delegate to this subagent when you need a release-artifact@2 generated from a collection of changeset@2 entries. Input is a list of changeset@2 JSON objects, the prior released version string, and a release date in YYYY-MM-DD format. Each input changeset already carries consumerimpact and semverimpact, set at…
release_chef
Manages versioning, changelog entries, release tags, and identifies breaking changes. Consulted post-cooking when preparing for release.
github-researcher
Use when you need to research official docs and GitHub examples, archive patterns, and avoid raw activation.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.