opensource-packager

opensource-packager is an agent for Claude Code from raja21068/AutoResearch. It costs 58 tokens per session (1,757 once invoked), scanned A, a copy of opensource-packager, MIT.

An open-source packaging agent that prepares a cleaned project for public use. It creates setup instructions, documentation, a license, contribution guidance, and GitHub issue templates when applicable.

In plain words
What is it for?
Use it to inspect a project’s technology stack and structure, create or improve README.md, add CLAUDE.md and setup.sh, choose packaging files, and prepare contribution and issue-reporting materials.
Why use it?
It removes the repeated setup and documentation work needed before others can run, understand, contribute to, or report problems in a repository.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; mentions CLAUDE.md; mentions Claude Code.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/user/opensource-staging/my-api,.

Good fit Use it to inspect a project’s technology stack and structure, create or improve README.md, add CLAUDE.md and setup.sh, choose packaging files, and prepare contribution and issue-reporting materials.

Compare 6 agents from other repositories ↓
Install

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.

Made for: Claude Code.

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.

agentmods badge for opensource-packager

README.md
[![agentmods](https://agentmods.dev/badge/agents/raja21068/autoresearch/opensource-packager/github.svg)](https://agentmods.dev/agents/raja21068/autoresearch/opensource-packager)
Your own site
<a href="https://agentmods.dev/agents/raja21068/autoresearch/opensource-packager"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/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.

agentmods 80×15 button for opensource-packager

Your own site · 80×15
<a href="https://agentmods.dev/agents/raja21068/autoresearch/opensource-packager"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/opensource-packager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
Origin 89% 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.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

Measured 1mo ago against content hash 133503decda4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

Origin

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.

skills/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. 1mo 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 raja21068/AutoResearch (2 stars, last pushed 5mo 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.

Related

Other agents, from other repositories

debugging-toolkit-dx-optimizer

Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.

wshobson/agents · 44 tokens

vibe-environment-worker

Runs a vibe session's Vercel environment in the target repository for the vibe and handoff orchestrators. Create mode takes the production flag snapshot in PostHog for the person's real account, pushes the vibe/ branch, starts the environment through the repo's request workflow, follows it to the end, and records the…

closedloop-ai/claude-plugins · 217 tokens

Orchestrator-Multi

Multi-agent parallel orchestrator using git worktrees — splits work across N agents, manages territory, merges results.

intellegix/intellegix-code-agent-toolkit · 27 tokens

vibe-seed-pr-worker

Handles the git and GitHub side of a vibe-seed-refresh pull request in the target repository for its orchestrator. Modes: open (push, PR from the template), push (push a fix the orchestrator committed and reply on its review threads), status (one-line PR state), sync (stage a merge of main for the orchestrator to…

closedloop-ai/claude-plugins · 106 tokens

pr-reviewer

Reviews PRs for version bump compliance, KISS/DRY violations, and cross-cutting concerns. Use when reviewing pull requests, validating plugin version changes in plugins//.claude-plugin/plugin.json, or checking files skipped by specialist agents (.githooks, config files, shell scripts, markdown). Triggers on PR review…

closedloop-ai/claude-plugins · 79 tokens

ops-deploy

Secure deployment with pre-deploy checklist. Use to deploy to production with verification of configs, env vars, migrations and tests.

christopherlouet/claude-base · 29 tokens