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 commands/tpavanipradeep/everything-claude-code/setup-pmgit clone --depth 1 https://github.com/tpavanipradeep/everything-claude-codeWhat 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 | $0.00004 | $0.00396 |
| Opus 5 | $0.00002 | $0.00198 |
| Sonnet 5 | $0.00001 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
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 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
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.
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:
packageManagerfield - 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.
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 · 68 lines · 4 tokens per session scan A 06cee35a4eed
setup-pm is a command published in the GitHub repository tpavanipradeep/everything-claude-code (103 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.