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.
npx agentmods add agents/fmarzochi/egc/opensource-packagergit clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/fmarzochi/egc/opensource-packager)<a href="https://agentmods.dev/agents/fmarzochi/egc/opensource-packager"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/opensource-packager.svg" alt="Measured on agentmods" 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.00057 | $0.01758 |
| Opus 5 | $0.00028 | $0.00879 |
| Sonnet 5 | $0.00011 | $0.00352 |
| 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 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.
This is a copy
88% identical to opensource-packager — 62 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 — 251 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 Gemini Code.
Your Role
- Analyze project structure, stack, and purpose
- Generate
GEMINI.md(the most important file: gives Gemini 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 GEMINI.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.
- 2d ago First seen · 251 lines · 57 tokens per session scan A 98ee72f96391
opensource-packager is an agent published in the GitHub repository Fmarzochi/EGC (48 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 1,758 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to opensource-packager, differing in 62 lines, and is treated as a copy.
Other agents, from other repositories
change-reviewer
Reviews structural changes (new modules, refactors, schema changes) for architecture conformance, naming conventions, layer violations, and missing ADRs. Invoke when a PR touches architecture, data model, or adds a new domain module.
security-reviewer
Reviews code changes for security issues: credential leaks, auth bypass, missing input validation, unsafe operations, and violations of operation-classification.md. Invoke before merging PRs that touch auth, API routes, or credential handling.
test-hunter
Generates adversarial tests for a module or feature. Does NOT write happy-path tests — that is the author's job. Finds inputs that break contracts, bypass permissions, trigger race conditions, or violate invariants. Invoke when a module has a base suite and needs adversarial hardening, before merging a sensitive…
spec-guardian
Verifies the codebase is in sync with the spec (PRD.md, use-cases.md, ADRs, data-model.md). Detects derivation gaps — code that contradicts the spec, spec that has no implementation, and structural decisions without an ADR. Invoke before cutting a release or when drift is suspected.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
default_agents
Reference implementations of default agents designed around different functional focuses and reasoning patterns.