ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.
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/affaan-m/ECCnpx agentmods add commands/affaan-m/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/affaan-m/ecc/setup-pm)<a href="https://agentmods.dev/commands/affaan-m/ecc/setup-pm"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/setup-pm/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/affaan-m/ecc/setup-pm"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/setup-pm.svg" alt="Reviewed on agentmods" width="80" 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.00396 |
| Opus 5.5 | $0.00002 | $0.00158 |
| Sonnet 5.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 1mo 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.
Copies of this mod
8 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
- setup-pm — 100% identical, 0 lines differ
- setup-pm — 100% identical, 0 lines differ
- setup-pm — 100% identical, 0 lines differ
- setup-pm — 94% identical, 2 lines differ
- setup-pm — 91% identical, 2 lines differ
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.
- 1mo ago First seen · 68 lines · 4 tokens per session scan A 06cee35a4eed
setup-pm is a command published in the GitHub repository affaan-m/ECC (284,906 stars, last pushed today), licensed MIT. It adds 4 tokens to every session and 396 once invoked, about $0.0000 per session on Opus 5.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-09-03.
Other commands, from other repositories
amend-plan
Plan Amend - Discuss and apply amendments to a plan.json implementation plan.
dev
You are an experienced Tech Lead overseeing multiple AI Worker Agents on software projects. The user is the PM / product owner. You drive all technical execution and communicate in natural language.
t00-new-pj
A command for starting a new T00 project by asking planning questions, assigning a project number, creating a folder and project file, and updating the project index. T00 appears to be a local project-management setup.
t00-estimate
A command that estimates whether a requested software task is practical before implementation and reports what was completed afterward. It uses different report formats depending on whether the user asks to start work or review the result.
t00-pj-status
A command that reads project files and lists the status and next step for each active project. You can also request a detailed to-do list for one project.
t00-status
A status-report command for a T00 task workspace, using files that record communication, tasks, and the previous session's next steps.