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.
curl -O https://raw.githubusercontent.com/Fmarzochi/EGC/main/.opencode/commands/setup-pm.mdgit 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/commands/fmarzochi/egc/setup-pm)<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.
<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>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.00004 | $0.00478 |
| Opus 5.5 | $0.00002 | $0.00191 |
| Sonnet 5.5 | $0.00001 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
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.
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.
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
- Environment variable:
EGC_PACKAGE_MANAGER(the oldGEMINI_PACKAGE_MANAGERstill counts) - Project config:
.egc/package-manager.json(an old.gemini/package-manager.jsonis still read) - package.json:
packageManagerfield - Lock file: Auto-detect from lock files
- Global config:
package-manager.jsonin the EGC directory of the active tool (or in the directoryEGC_DIRnames when it is set) - 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.
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.
- 13d ago Changed · +2 lines 88651b54fd8c
- 1mo ago First seen · 68 lines · 4 tokens per session scan A b2fa8b1033a5
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.
Other commands, from other repositories
status
Display project status, active tracks, and next actions.
test-management
Organize, classify, and trace Katalon True Platform/TestOps test assets. Use when you need to structure test cases into folders and suites, move or reorganize cases, search and find existing assets at scale, link or unlink requirements to test cases, or produce a requirement-to-test traceability report (which…
pm-charter
Create, import, discover, approve, or skip project charter. No-arg form is an interactive wizard.
_closing
A set of closing rules for project-management commands that change the .pm/ project-management folder. It controls the language of summaries and links shown in the final response.
implement-approved-slice
Implement only the approved slice with minimal changes, then persist execution evidence in slice notes and TASKSTATE.md. The official execution path. Opt-in test-first mode via --tdd. Use when the plan and slice are approved, ambiguity is resolved and files in scope are known. Do not use during discovery or planning…
project_init
A command that starts tracking a project with ocul-pm by creating its project records and agent logging rules.