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/sushaantu/boxento/package-managementgit clone --depth 1 https://github.com/sushaantu/boxentoWhat 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.00203 |
| Opus 5 | $0.00000 | $0.00102 |
| Sonnet 5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
package-management 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 today.
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
- Use Bun as the primary package manager
- All scripts in package.json should use bun commands
- Use
bun installfor dependency installation - Use
bun runfor running scripts - Maintain a single bun.lockb file at the root
- Use workspace features for monorepo management if applicable
- Pin dependency versions for production dependencies
- Organize package.json sections consistently (dependencies, devDependencies, scripts, etc.)
- Include appropriate type declarations (@types/*) for all dependencies
- Regularly audit dependencies for security vulnerabilities with
bun pm audit - Document script usage in README.md or CONTRIBUTING.md
- Group related dependencies in package.json with comments
- Use Bun's built-in test runner for unit tests
- Leverage Bun's TypeScript support without the need for ts-node
- Optimize package.json scripts with Bun's fast execution capabilities
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.
- today First seen · 20 lines · 203 tokens per session scan A 4da1695f794c
package-management is a cursor rule published in the GitHub repository sushaantu/boxento (153 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 203 tokens. 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-01.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.