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.
git clone --depth 1 https://github.com/kwami-labs/kwamiWrote 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/rules/kwami-labs/kwami/js-package-manager)<a href="https://agentmods.dev/rules/kwami-labs/kwami/js-package-manager"><img src="https://agentmods.dev/badge/rules/kwami-labs/kwami/js-package-manager/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/rules/kwami-labs/kwami/js-package-manager"><img src="https://agentmods.dev/badge/rules/kwami-labs/kwami/js-package-manager.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.00255 | $0.00255 |
| Opus 5.5 | $0.00102 | $0.00102 |
| Sonnet 5.5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
js-package-manager 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.
What it actually says
JS package manager
Never default to npm for install, scripts, or CI in this repo.
Detection (pick one)
bun.lock/bun.lockb→ bunpnpm-lock.yaml/pnpm-workspace.yaml→ pnpm- Otherwise → pnpm (default)
This repo uses pnpm (pnpm-lock.yaml).
Do / don't
# ✅
pnpm install --frozen-lockfile
pnpm lint && pnpm typecheck && pnpm test:run && pnpm build
# ❌
npm ci
npm install
npm run …
CI
- Use
pnpm/action-setup(or bun’s setup action) beforeactions/setup-node - Set
cache: "pnpm"(or"bun") — nevercache: "npm"unless onlypackage-lock.jsonexists - Install with
pnpm install --frozen-lockfile(orbun install --frozen-lockfile)
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 · 36 lines · 255 tokens per session scan A 8d866d297769
js-package-manager is a cursor rule published in the GitHub repository kwami-labs/kwami (49 stars, last pushed 5d ago), licensed Apache-2.0. It adds 255 tokens to every session, about $0.0010 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-08-30.
Other cursor rules, from other repositories
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
write
Writing style guide with AI detection avoidance. For tweets, LinkedIn, blogs, READMEs, commits. Activate with @write.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.
architecture
Architectural and cross-package changes — dependency direction, editor/runtime boundaries, scene schema, persistence, renderer packages. Use when changing package boundaries, serialized formats, or multiple layers. Do not apply to localized UI, styling, or test-only edits.
readme-best-practices
README Best Practices - enforces high-quality README patterns when creating or editing README files.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.