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/mturac/everything-openai-codex/setup-pmgit clone --depth 1 https://github.com/mturac/everything-openai-codexWrote 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/mturac/everything-openai-codex/setup-pm)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/setup-pm"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/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.00401 |
| Opus 5 | $0.00002 | $0.00200 |
| 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
88% identical to setup-pm — 18 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:
CODEX_PACKAGE_MANAGER - Project config:
.codex/package-manager.json - package.json:
packageManagerfield - Lock file: Auto-detect from lock files
- Global config:
~/.codex/package-manager.json - Fallback: First available
Configuration Options
Option 1: Environment Variable
export CODEX_PACKAGE_MANAGER=pnpm
Option 2: Project Config
# Create .codex/package-manager.json
echo '{"packageManager": "pnpm"}' > .codex/package-manager.json
Option 3: package.json
{
"packageManager": "[email protected]"
}
Option 4: Global Config
# Create ~/.codex/package-manager.json
echo '{"packageManager": "yarn"}' > ~/.codex/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 d95ced2aef27
setup-pm is a command published in the GitHub repository mturac/everything-openai-codex (89 stars, last pushed 12d ago), licensed MIT. It adds 4 tokens to every session and 401 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to setup-pm, differing in 18 lines, and is treated as a copy.
Other commands, from other repositories
update-faq
could you please update DESIGNFAQ & DXFAQ based on the changes we are trying to achieve.
feature
Orchestrate a complete feature through discovery, spec, implementation, and review.
research
Research a technical or product question.
selfloop
Start or control a persistent SIPS loop whose only objective is improving SIPS and the agent operating it through measured, verified iterations.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
patterns
Show the full agentpatterns report — success rate, approach→outcome correlation, top patterns.