EGC: Command for Claude Code

.opencode/commands/setup-pm.md

setup-pm is a command for Claude Code, OpenCode from Fmarzochi/EGC. It costs 4 tokens per session (478 once invoked), scanned A, a copy of setup-pm, Apache-2.0.

A project configuration command that chooses which package manager the project should use, such as npm, pnpm, yarn, or bun. A package manager installs dependencies and runs project scripts.

In plain words
What is it for?
Use it to configure or detect the package manager for a project or globally, with fallback detection when no preference is set.
Why use it?
It prevents inconsistent dependency and script commands by recording or detecting one package manager preference from configuration, environment variables, or lock files.

Command for Claude CodeOpenCode

Written for Claude Code and OpenCode: $ARGUMENTS substitution, but also installed under .opencode/. Also seen: agent in frontmatter.

This is Fmarzochi/EGC's own configuration. It tells Claude Code and OpenCode how to work on EGC itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything EGC configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/setup-package-manager.js --detect.

Reuse

Borrowing it

Nothing to install: this file belongs to Fmarzochi/EGC. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Fmarzochi/EGC/main/.opencode/commands/setup-pm.md
Clone the repo
git clone --depth 1 https://github.com/Fmarzochi/EGC

Made for: Claude Code, OpenCode.

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 setup-pm

README.md
[![agentmods](https://agentmods.dev/badge/commands/fmarzochi/egc/setup-pm/github.svg)](https://agentmods.dev/commands/fmarzochi/egc/setup-pm)
Your own site
<a href="https://agentmods.dev/commands/fmarzochi/egc/setup-pm"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/setup-pm/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 setup-pm

Your own site · 80×15
<a href="https://agentmods.dev/commands/fmarzochi/egc/setup-pm"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/setup-pm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 478 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 86% 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.00004 $0.00478
Opus 5.5 $0.00002 $0.00191
Sonnet 5.5 $0.00001 $0.00096
Haiku 4.5 $0.00000 $0.00048

Measured 13d ago against content hash 88651b54fd8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup-pm 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 13d 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

86% identical to setup-pm — 22 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.

.opencode/commands/setup-pm.md · 70 lines

What it actually says

Setup Package Manager Command

Configure your preferred package manager: $ARGUMENTS

Your Task

Set up package manager preference for the project or globally.

Detection Order

  1. Environment variable: EGC_PACKAGE_MANAGER (the old GEMINI_PACKAGE_MANAGER still counts)
  2. Project config: .egc/package-manager.json (an old .gemini/package-manager.json is still read)
  3. package.json: packageManager field
  4. Lock file: Auto-detect from lock files
  5. Global config: package-manager.json in the EGC directory of the active tool (or in the directory EGC_DIR names when it is set)
  6. Fallback: First available

Configuration Options

Option 1: Environment Variable

export EGC_PACKAGE_MANAGER=pnpm

Option 2: Project Config

# Create .egc/package-manager.json
echo '{"packageManager": "pnpm"}' > .egc/package-manager.json

Option 3: package.json

{
  "packageManager": "[email protected]"
}

Option 4: Global Config

Create package-manager.json in the EGC directory of the active tool (the directory EGC_DIR names when it is set; otherwise the one EGC uses for the tool in session, where its sessions and learned skills live):

{
  "packageManager": "yarn"
}

Supported Package Managers

Manager Lock File Commands
npm package-lock.json npm install, npm run
pnpm pnpm-lock.yaml pnpm install, pnpm run
yarn yarn.lock yarn install, yarn run
bun bun.lockb bun install, bun run

Verification

Check current setting:

node scripts/setup-package-manager.js --detect

TIP: For consistency across team, add packageManager field to package.json.

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. 13d ago Changed · +2 lines 88651b54fd8c
  2. 1mo ago First seen · 68 lines · 4 tokens per session scan A b2fa8b1033a5

Subscribe to this mod's changes

setup-pm is a command published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed today), licensed Apache-2.0. It adds 4 tokens to every session and 478 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to setup-pm, differing in 22 lines, and is treated as a copy.