A command for choosing which package manager a project should use, such as npm, pnpm, Yarn, or Bun. It can save the choice in project or global configuration and can detect an existing choice.

Use it when setting up a project, changing its package-manager preference, or checking how that preference is detected.

It prevents inconsistent install and run commands across developers and helps the project follow its lock file or declared package-manager setting.

How yapota2018/affaan-m-everything-claude-code configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to yapota2018/affaan-m-everything-claude-code. 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/yapota2018/affaan-m-everything-claude-code/main/.opencode/commands/setup-pm.md

Clone the repo

git clone --depth 1 https://github.com/yapota2018/affaan-m-everything-claude-code

Made for: Claude Code, OpenCode.

Or install everything-claude-code, the plugin that ships this one along with the rest of its 29 skills, 29 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/yapota2018/affaan-m-everything-claude-code/setup-pm.svg)](https://agentmods.dev/commands/yapota2018/affaan-m-everything-claude-code/setup-pm)

Your own site

<a href="https://agentmods.dev/commands/yapota2018/affaan-m-everything-claude-code/setup-pm"><img src="https://agentmods.dev/badge/commands/yapota2018/affaan-m-everything-claude-code/setup-pm.svg" alt="Measured on agentmods" 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 396 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 100% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00004	$0.00396
Opus 5	$0.00002	$0.00198
Sonnet 5	$0.00001	$0.00079
Haiku 4.5	$0.00000	$0.00040

Measured 7d ago against content hash 06cee35a4eed, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-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 7d 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

100% identical to setup-pm — 0 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 · 68 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

Environment variable: CLAUDE_PACKAGE_MANAGER
Project config: .claude/package-manager.json
package.json: packageManager field
Lock file: Auto-detect from lock files
Global config: ~/.claude/package-manager.json
Fallback: First available

Configuration Options

Option 1: Environment Variable

export CLAUDE_PACKAGE_MANAGER=pnpm

Option 2: Project Config

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

Option 3: package.json

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

Option 4: Global Config

# Create ~/.claude/package-manager.json
echo '{"packageManager": "yarn"}' > ~/.claude/package-manager.json

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.

7d ago First seen · 68 lines · 4 tokens per session scan A 06cee35a4eed

Subscribe to this mod's changes

setup-pm is a command published in the GitHub repository yapota2018/affaan-m-everything-claude-code (4 stars, last pushed 5mo ago), licensed MIT. It adds 4 tokens to every session and 396 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to setup-pm, differing in 0 lines, and is treated as a copy.

affaan-m-everything-claude-code: Command for Claude Code