setup-pm

setup-pm is a command for Claude Code from Galaxy-Dawn/claude-scholar. It costs 14 tokens per session (404 once invoked), scanned A, original, MIT.

A command that selects and records the package manager a JavaScript project should use, such as npm, pnpm, yarn, or bun. It can detect the choice from project files, environment settings, lock files, or available programs.

In plain words
What is it for?
Use it to detect the current package manager, set a project or global preference, or list the supported package managers.
Why use it?
It avoids inconsistent dependency-install commands across developers and projects. The configuration can be set for one project or globally.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths.

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.

Part of the claude-scholar plugin — 45 skills, 34 commands, 6 agents, 5 hooks shipped together

Good fit Use it to detect the current package manager, set a project or…

Compare 6 commands from other repositories ↓
About the project

Claude Scholar is a semi-automated research assistant for academic research and software development, supporting literature review, coding, experiments, reporting, writing, and project knowledge management. Computer science and AI researchers use it across the research workflow with several coding-agent platforms; the catalogue contains its skills, commands, agents, hooks, plugin, and instruction.

Galaxy-Dawn/claude-scholar · 5,336 stars · on GitHub

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar
agentmods
npx agentmods add commands/galaxy-dawn/claude-scholar/setup-pm

Made for: Claude Code.

Or install claude-scholar, the plugin that ships this one along with the rest of its 45 skills, 34 commands, 6 agents, 5 hooks.

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/galaxy-dawn/claude-scholar/setup-pm.svg)](https://agentmods.dev/commands/galaxy-dawn/claude-scholar/setup-pm)
Your own site
<a href="https://agentmods.dev/commands/galaxy-dawn/claude-scholar/setup-pm"><img src="https://agentmods.dev/badge/commands/galaxy-dawn/claude-scholar/setup-pm.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 404 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 original No closer match found 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.00014 $0.00404
Opus 5 $0.00007 $0.00202
Sonnet 5 $0.00003 $0.00081
Haiku 4.5 $0.00001 $0.00040

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

Copies of this mod

5 near-identical copies found in the catalogue:

  • setup-pm — 100% identical, 0 lines differ
  • setup-pm — 100% identical, 0 lines differ
  • setup-pm — 100% identical, 0 lines differ
  • ccc-setup-pm — 100% identical, 2 lines differ
  • setup-pm — 89% identical, 3 lines differ
commands/setup-pm.md · 81 lines

What it actually says

Package Manager Setup

Configure your preferred package manager for this project or globally.

Usage

# Detect current package manager
node scripts/setup-package-manager.js --detect

# Set global preference
node scripts/setup-package-manager.js --global pnpm

# Set project preference
node scripts/setup-package-manager.js --project bun

# List available package managers
node scripts/setup-package-manager.js --list

Detection Priority

When determining which package manager to use, the following order is checked:

  1. Environment variable: CLAUDE_PACKAGE_MANAGER
  2. Project config: .claude/package-manager.json
  3. package.json: packageManager field
  4. Lock file: Presence of package-lock.json, yarn.lock, pnpm-lock.yaml, or bun.lockb
  5. Global config: ~/.claude/package-manager.json
  6. Fallback: First available package manager (pnpm > bun > yarn > npm)

Configuration Files

Global Configuration

// ~/.claude/package-manager.json
{
  "packageManager": "pnpm"
}

Project Configuration

// .claude/package-manager.json
{
  "packageManager": "bun"
}

package.json

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

Environment Variable

Set CLAUDE_PACKAGE_MANAGER to override all other detection methods:

# Windows (PowerShell)
$env:CLAUDE_PACKAGE_MANAGER = "pnpm"

# macOS/Linux
export CLAUDE_PACKAGE_MANAGER=pnpm

Run the Detection

To see current package manager detection results, run:

node scripts/setup-package-manager.js --detect
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. 7d ago First seen · 81 lines · 14 tokens per session scan A 163b3cd10602

Subscribe to this mod's changes

setup-pm is a command published in the GitHub repository Galaxy-Dawn/claude-scholar (5,336 stars, last pushed 10d ago), licensed MIT. It adds 14 tokens to every session and 404 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.