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/pranav-karra-3301/tuck/dependenciesgit clone --depth 1 https://github.com/Pranav-Karra-3301/tuckWrote 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/pranav-karra-3301/tuck/dependencies)<a href="https://agentmods.dev/rules/pranav-karra-3301/tuck/dependencies"><img src="https://agentmods.dev/badge/rules/pranav-karra-3301/tuck/dependencies.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.00469 |
| Opus 5 | $0.00000 | $0.00234 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
dependencies 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 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.
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
Dependency Rules
Package Manager
ALWAYS use pnpm:
pnpm install # Install deps
pnpm add <pkg> # Add dependency
pnpm add -D <pkg> # Add dev dependency
pnpm remove <pkg> # Remove dependency
pnpm update # Update all deps
NEVER use npm or yarn commands.
Core Dependencies
| Package | Purpose | Version |
|---|---|---|
| commander | CLI framework | ^12.x |
| @clack/prompts | Interactive prompts | ^0.7.x |
| chalk | Terminal colors | ^5.x |
| boxen | Terminal boxes | ^8.x |
| ora | Spinners | ^8.x |
| simple-git | Git operations | ^3.x |
| fs-extra | File operations | ^11.x |
| zod | Schema validation | ^3.x |
Dev Dependencies
| Package | Purpose |
|---|---|
| typescript | Type checking |
| tsup | Bundling |
| vitest | Testing |
| eslint | Linting |
| prettier | Formatting |
| @types/* | Type definitions |
Version Pinning
- Use caret (^) for minor updates
- Pin major versions
- Lock file must be committed
Security Audits
Run regularly:
pnpm audit
pnpm audit --fix # Auto-fix if possible
CI runs pnpm audit --audit-level=high
Adding Dependencies
Before adding a new dependency:
- Check if existing dep can do it
- Verify it supports ESM
- Check maintenance status
- Review bundle size impact
- Prefer deps with TypeScript types
Updating Dependencies
- Check for breaking changes
- Run full test suite
- Test manually
- Update in feature branch
pnpm update --interactive # Select updates
pnpm outdated # Check outdated
NEVER Do
- Use
npm install - Commit without lock file
- Ignore security warnings
- Add unnecessary deps
- Use deps without ESM support
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 · 89 lines · 0 tokens per session scan A 7c93e69c73ea
dependencies is a cursor rule published in the GitHub repository Pranav-Karra-3301/tuck (15 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 469 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-08-30.
Other cursor rules, from other repositories
architecture
Architecture of openapi-to-cli (ocli).
github-workflow
GitHub invariants — standard flow on listed use cases; no issue spam; tick linked checklists before merge.
skill-selection
Pick the fewest skills for this task. Core lifecycle for non-trivial work; extras only on a matching signal. Catalog is using-agent-skills, not this rule.
conservative-file-creation
Check for existing files before creating. Be conservative about new files and code.
repository-layout
Canonical map of repo folders and docs.
research-before-suggesting
Never make up features, APIs, or config options. Research before suggesting technical solutions.