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 rules/dmenchaca/webflow-to-react/npm-ci-reproducibilitygit clone --depth 1 https://github.com/dmenchaca/webflow-to-reactWrote 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/dmenchaca/webflow-to-react/npm-ci-reproducibility)<a href="https://agentmods.dev/rules/dmenchaca/webflow-to-react/npm-ci-reproducibility"><img src="https://agentmods.dev/badge/rules/dmenchaca/webflow-to-react/npm-ci-reproducibility.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 | $0.00000 | $0.00390 |
| Opus 5 | $0.00000 | $0.00195 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade C, and why
npm-ci-reproducibility scanned grade C with 1 finding 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
cd web && rm -rf node_modules && npm ci && npm run build What it actually says
npm ci and reproducible installs (web/)
Netlify (and most CI) runs npm ci in web/ when web/package-lock.json exists. npm ci installs exactly what the lockfile pins — not “whatever npm install resolves today”.
Rules
- After any change to
web/package.jsonor intentional dependency bump: runnpm installinsideweb/, then verifynpm cifrom a clean tree:cd web && rm -rf node_modules && npm ci && npm run build - Commit
web/package-lock.jsonin the same commit asweb/package.jsonchanges. - For repos that deploy, prefer exact versions (or tight ranges you control) on
@tanstack/*and other core deps — avoid"latest"so installs stop drifting between laptops and CI. ETARGET/ lock failures on CI: regenerate the lockfile locally afternpm install; if a transitive stays broken, add a documentedpackage.jsonoverridesentry as a last resort.
Full context: gotchas.md § npm ci, lockfiles, and "latest", shipping.md § Lockfile and CI parity.
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.
- 5d ago First seen · 22 lines · 0 tokens per session scan C 730dfd1c9cd2
npm-ci-reproducibility is a cursor rule published in the GitHub repository dmenchaca/webflow-to-react (27 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 390 tokens. A static security scan graded it C with 1 finding (recursive force delete). 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
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
NewGroup
Guidance on how to add details.json files for new social groups.
infrastructure
Terraform infrastructure-as-code standards for multi-cloud (AWS, GCP, Azure, OCI) provisioning.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.