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/sifxprime/kodelyth-eccnpx agentmods add commands/sifxprime/kodelyth-ecc/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/sifxprime/kodelyth-ecc/setup-pm)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/setup-pm"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/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.00014 | $0.00404 |
| Opus 5 | $0.00007 | $0.00202 |
| Sonnet 5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00001 | $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
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:
- Environment variable:
CLAUDE_PACKAGE_MANAGER - Project config:
.claude/package-manager.json - package.json:
packageManagerfield - Lock file: Presence of package-lock.json, yarn.lock, pnpm-lock.yaml, or bun.lockb
- Global config:
~/.claude/package-manager.json - 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
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 · 81 lines · 14 tokens per session scan A 163b3cd10602
setup-pm is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 4d 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. It is 100% identical to setup-pm, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
maintainer-standup
Synthesize the maintainer's morning standup brief from gathered git/PR/issue/state data.
workflow-status
Show Agent Workflow Kit workflow run status.
workflows
List Agent Workflow Kit workflow runs.
dev-shift
Jalankan continuous dev shift untuk project aktif: agent memilih task, mengeksekusi, QA, review, dan mendokumentasikan berulang sampai durasi habis — tanpa prompt baru per task.
new-project
Buat folder project baru di project/{id}/ beserta dokumentasi pengembangan.
adopt-roadmap.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.