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/aiagentwithdhruv/ai-dev-stack/90-devops-deploymentgit clone --depth 1 https://github.com/aiagentwithdhruv/ai-dev-stackWhat 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.00585 |
| Opus 5 | $0.00000 | $0.00293 |
| Sonnet 5 | $0.00000 | $0.00117 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
90-devops-deployment 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 2d 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
Deployment targets:
- Docker for packaging.
- AWS (ECS Fargate, Lambda, S3) for scalable cloud deployment.
- Vercel for frontend and serverless Next.js deployments.
- VPS (Ubuntu/Debian) for cost-effective long-running services.
- CI/CD for validation and release automation.
DevOps rules:
- Applications must be container-friendly.
- Keep builds reproducible.
- Use environment-driven configuration.
- Separate build-time config from runtime config.
- Add health checks where appropriate.
- Keep services stateless unless statefulness is intentional and documented.
- Ensure logs are structured and production-usable.
Docker expectations:
- Keep Dockerfiles clean and optimized.
- Prefer multi-stage builds when useful.
- Avoid baking secrets into images.
- Minimize image size where practical.
- Use .dockerignore to exclude node_modules, .env, .git, checkpoints.
AWS expectations:
- Prefer managed services where appropriate.
- Use least-privilege IAM policies.
- Make networking and environment assumptions explicit.
- Support observability via logs, metrics, and alarms.
- Design for rollback-safe deployments.
Vercel expectations:
- Use vercel.json for project configuration.
- Set environment variables via Vercel dashboard, never in code.
- Use Edge/Serverless functions for API routes.
- Keep build output under Vercel size limits.
- Use preview deployments for PR review.
- Configure custom domains and redirects in vercel.json.
- Use Vercel Analytics and Speed Insights where available.
VPS expectations:
- Use systemd or PM2 for process management.
- Set up Nginx/Caddy as reverse proxy with SSL (Let's Encrypt).
- Use UFW or iptables for firewall — only expose necessary ports.
- Set up unattended-upgrades for security patches.
- Use SSH keys only — disable password auth.
- Keep deployment scripted and repeatable (shell scripts or Ansible).
- Monitor with basic tooling: htop, journalctl, logrotate.
CI/CD expectations:
- Run lint, tests, and build validation before merge/deploy.
- Prevent obviously broken releases.
- Keep deployment config version-controlled.
- Use separate environments where needed, e.g. dev/staging/production.
- Use GitHub Actions for CI, Vercel for frontend CD, and scripts for VPS CD.
Do not:
- Hardcode AWS-specific IDs, Vercel tokens, or VPS IPs in code.
- Mix deployment-only hacks into application logic.
- Assume local-only paths/config in production code.
- Run services as root on VPS.
- Expose database ports publicly on any platform.
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.
- 2d ago First seen · 67 lines · 0 tokens per session scan A b709dba3b723
90-devops-deployment is a cursor rule published in the GitHub repository aiagentwithdhruv/ai-dev-stack (10 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 585 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-31.
Other cursor rules, from other repositories
cursorrules
You are building an AI/ML project with Python. The project uses PyTorch for model training, handles data pipelines with proper validation, tracks experiments systematically, and follows production ML engineering practices. Code is type-hinted, tested, and reproducible.
cursorrules
Code exhibits taste — Torvalds' term for finding the formulation where special cases disappear. Seek representations where edge cases become impossible, the type system proves correctness, and the API guides users into the pit of success.
angular
Angular: signals, standalone components, RxJS patterns.
django
Django: models, views, ORM best practices.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.