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 skills add girijashankarj/cursor-handbook --skill infrastructuregit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/skills/girijashankarj/cursor-handbook/infrastructure)<a href="https://agentmods.dev/skills/girijashankarj/cursor-handbook/infrastructure"><img src="https://agentmods.dev/badge/skills/girijashankarj/cursor-handbook/infrastructure/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/skills/girijashankarj/cursor-handbook/infrastructure"><img src="https://agentmods.dev/badge/skills/girijashankarj/cursor-handbook/infrastructure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.00527 |
| Opus 5 | $0.00012 | $0.00264 |
| Sonnet 5 | $0.00005 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
infrastructure 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Set Up Cloud Infrastructure
Trigger
When the user needs to create or modify cloud resources.
Steps
Step 1: Define Requirements
- What resources are needed?
- Which environment? (dev, staging, production)
- Performance requirements?
- Budget constraints?
- Security requirements?
Step 2: Design Architecture
- Draw architecture diagram (Mermaid)
- Define networking (VPC, subnets, security groups)
- Plan compute resources (size, scaling)
- Plan storage (database, file storage, cache)
- Plan monitoring and alerting
Step 3: Write IaC
- Create Terraform/CDK/CloudFormation templates
- Use modules for reusable components
- Parameterize environment-specific values
- Follow naming conventions:
{project}-{env}-{resource} - Tag all resources
Step 4: Security
- Enable encryption at rest
- Enable encryption in transit
- Configure IAM with least privilege
- Set up VPC and security groups
- Enable audit logging
Step 5: Deploy
- Plan: Review changes before applying
- Apply to dev first
- Verify in dev
- Promote to staging
- Verify in staging
- Promote to production
Step 6: Monitor
- Set up health checks
- Configure alert rules
- Create dashboards
- Set up cost alerts
If a step fails
| Step | Failure | Recovery |
|---|---|---|
| Step 5 | Deploy to dev/staging fails | Run terraform destroy or equivalent; fix IaC; re-apply; never proceed to prod until dev/staging succeeds |
| Step 5 | Deploy to production fails | Rollback via IaC (revert and apply previous state); investigate; fix in dev; re-test full pipeline |
| Step 5 | Partial apply (some resources created) | Document what was created; run destroy/rollback for failed resources; fix and retry |
Never apply infrastructure changes to production without explicit user confirmation. Require confirmation before terraform apply or equivalent on prod.
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 · 67 lines · 24 tokens per session scan A 57414f14dbe5
infrastructure is a skill published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 9d ago), licensed MIT. It adds 24 tokens to every session and 527 once invoked, about $0.0001 per session on Opus 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-09-03.
Other skills, from other repositories
deploy-verify
Post-deploy smoke test across browser, Sentry, Supabase, Langfuse, and the public web. Use when "verify deploy", "smoke test production", "post-release check", or "ship or rollback". Deploy + observation loop → workflow-ship-and-observe. npm package release → deploy-npm.
backend-patterns
Apply backend patterns — queues, caching, rate limits, serverless/edge. Use when "queue jobs", "caching layer", "rate limiting", "server actions", or "edge function". Which architecture to pick → audit-backend-architecture.
audit-env-parity
Read-only audit of config/env parity across dev, staging, and prod — missing or misnamed vars, drifted flags, hardcoded values, secrets reused across environments. Use when "works locally but not in prod", "audit our environments", or "config drift". Local runnability → workflow-environment-ready.
audit-infra-cost
Read-only audit of hosting, database, storage, egress, and serverless spend (Supabase, Vercel, S3/R2, edge). Use when "hosting bill is high", "cut infra costs", or a bill jumps. CI minutes → audit-cicd. Model tokens → plan-llm-cost-guardrails. Consumes test-load numbers.
plan-backup-dr
Audit whether a project can actually recover from data loss — not just whether backups exist — then emit a phased DR plan. Use when "can we recover if the DB dies", "audit our backups", "what's our RPO/RTO", or "disaster recovery". Plan only. Destructive-op gates stay on plan-data-integrity.
nginx-config-optimizer
Optimizes Nginx configurations for performance, security, caching, and load balancing with modern best practices. Use when users request "Nginx setup", "reverse proxy", "load balancer", "web server config", or "Nginx optimization".