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.
git clone --depth 1 https://github.com/raja21068/AutoResearchnpx agentmods add commands/raja21068/autoresearch/setup-pmWrote 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/raja21068/autoresearch/setup-pm)<a href="https://agentmods.dev/commands/raja21068/autoresearch/setup-pm"><img src="https://agentmods.dev/badge/commands/raja21068/autoresearch/setup-pm.svg" alt="Measured on agentmods" 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.00402 |
| Opus 5 | $0.00002 | $0.00201 |
| Sonnet 5 | $0.00001 | $0.00080 |
| 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
91% identical to setup-pm — 2 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 1010086b91fb
setup-pm is a command published in the GitHub repository raja21068/AutoResearch (2 stars, last pushed 3mo ago), licensed MIT. It adds 4 tokens to every session and 402 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to setup-pm, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
implement
Execute tasks from a track's implementation plan following TDD workflow.
new-track
Create a new track with specification and phased implementation plan.
manage
Manage track lifecycle: archive, restore, delete, rename, and cleanup.
portfolio-status
Review the health of all projects in the portfolio.
autopilot-multi
Multi-story autopilot orchestrator — runs N parallel issue pipelines in isolated git worktrees (v3.6 Phase D thin-slice).
ops-standup
Morning briefing: commits, PRs, CI, blockers and priorities of the day.