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/sagar25-code-it/ps3d-cad-studio/deploymentgit clone --depth 1 https://github.com/sagar25-Code-it/ps3d-cad-studioWhat 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.00023 | $0.00689 |
| Opus 5 | $0.00012 | $0.00345 |
| Sonnet 5 | $0.00005 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
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 yesterday.
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
PS3D deployment context
deployment:
cloudProvider: Vercel with optional Supabase Marketplace integration
environments:
- name: local-development
purpose: developer workstation with Vite hot reload
runCommand: pnpm dev
- name: local-qualified-build
purpose: strict static-server browser and header verification of dist
runCommand: pnpm build
- name: local-mcp-stdio
purpose: stateless model-neutral MCP tools for a local compliant host
runCommand: pnpm mcp:stdio
- name: github-ci
purpose: approved clean environment for frozen install, typecheck, all tests, build, CodeQL, and dependency review
runCommand: GitHub Actions workflows under .github/workflows
- name: public-preview
purpose: reviewed public browser prototype, account portal, learning center, and remote MCP endpoint
deployMechanism: Vercel Git import from the new public GitHub repository
strategy:
type: immutable-static-artifact-plus-web-standard-functions
featureFlags: workspace capabilities declare implemented, preview, and unavailable states
serverBoundary: Vercel serves the browser artifact and api functions; local stdio remains optional; Supabase owns identity and tenant data
failClosed: account, token, OAuth consent, and remote MCP routes return configuration errors when required secrets are absent
rollback:
code: redeploy the previously qualified immutable static artifact or revert the reviewed change
database: use a reviewed forward migration or restore an owner-controlled Supabase backup; never edit token digests manually
config: revert vercel.json or host settings in a dedicated reviewed change
ci:
provider: GitHub Actions
prChecks: frozen install, typecheck, deterministic tests, production build, CodeQL, and dependency review
workflows:
- .github/workflows/ci.yml
- .github/workflows/codeql.yml
- .github/workflows/dependency-review.yml
securityHeaders:
source: vercel.json and scripts/strict-static-server.mjs
policy: restrictive CSP, no framing, strict referrer, HSTS, cross-origin isolation headers, no privileged browser APIs, immutable hashed assets
observability:
apm: TBD
logs: Vercel/Supabase platform logs only; no model payload persistence by PS3D functions
releaseGates:
- frozen dependency installation
- strict typecheck and executed tests
- production build and production-module boundary verification
- exact response-header and browser smoke verification
- dependency vulnerability, license, integrity, notice, and SBOM review
- lock-to-inventory dependency reconciliation and peer dependency check
- secret and private-path scans
- Supabase RLS, token isolation, expiry, revocation, quota, and verified-email checks
- live health, public config, access portal, OAuth metadata, initialize, tools/list, and one read-only MCP call
- deterministic build comparison and signed source or build identities
- human provenance, accessibility, security, and release approval
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.
- yesterday First seen · 70 lines · 23 tokens per session scan A 0cba7b1b2892
deployment is a cursor rule published in the GitHub repository sagar25-Code-it/ps3d-cad-studio (0 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 689 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-08-31.
Other cursor rules, from other repositories
180-terraform
Secure, efficient, modular Terraform with strong validation, docs, and CI hygiene.
devops-engineer
Infrastructure, Deployment, and CI/CD specialist. Use PROACTIVELY when a feature is ready to merge to handle deployments (Vercel, AWS, Docker), infrastructure-as-code (Terraform), and pipeline automation (GitHub Actions).
deployment-engineer
Designs and implements robust CI/CD pipelines, container orchestration, and cloud infrastructure automation. Proactively architects and secures scalable, production-grade deployment workflows using best practices in DevOps and GitOps.
viberaven-deploy
Apply before changing Vercel config or deploy CI workflows.
netlify-deploy
Create and manage Netlify deploys — Git continuous deployment, CLI manual/anonymous deploys, Deploy to Netlify buttons, drag-and-drop, and per-context netlify.toml build settings. Use when linking a repo, deploying from the CLI, setting up Deploy Previews or branch deploys, configuring deploy contexts, adding skew…
40-deploy
For PM2 processes, GitHub Actions, health checks, and production operations.