ps3d-cad-studio: Cursor rule for Cursor

.cursor/project-context/deployment.mdc

deployment is a cursor rule for Cursor from sagar25-Code-it/ps3d-cad-studio. It costs 23 tokens per session (689 once invoked), scanned A, original, MIT.

A deployment reference for PS3D, covering local development, GitHub CI, Vercel hosting, Supabase services, and remote model tools. It explains what each environment is for and how it is run or deployed.

In plain words
What is it for?
Use it when running the app locally, building it, starting local model tools, checking GitHub workflows, or deploying the public preview.
Why use it?
It prevents deployment changes from ignoring the differences between local builds, automated checks, the public preview, and remote services.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

This is sagar25-Code-it/ps3d-cad-studio's own configuration. It tells Cursor how to work on ps3d-cad-studio itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ps3d-cad-studio configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sagar25-Code-it/ps3d-cad-studio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sagar25-Code-it/ps3d-cad-studio/main/.cursor/project-context/deployment.mdc
Clone the repo
git clone --depth 1 https://github.com/sagar25-Code-it/ps3d-cad-studio

Made for: Cursor.

Wrote 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.

agentmods badge for deployment

README.md
[![agentmods](https://agentmods.dev/badge/rules/sagar25-code-it/ps3d-cad-studio/deployment/github.svg)](https://agentmods.dev/rules/sagar25-code-it/ps3d-cad-studio/deployment)
Your own site
<a href="https://agentmods.dev/rules/sagar25-code-it/ps3d-cad-studio/deployment"><img src="https://agentmods.dev/badge/rules/sagar25-code-it/ps3d-cad-studio/deployment/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.

agentmods 80×15 button for deployment

Your own site · 80×15
<a href="https://agentmods.dev/rules/sagar25-code-it/ps3d-cad-studio/deployment"><img src="https://agentmods.dev/badge/rules/sagar25-code-it/ps3d-cad-studio/deployment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 689 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00689
Opus 5.5 $0.00009 $0.00276
Sonnet 5.5 $0.00005 $0.00138
Haiku 4.5 $0.00002 $0.00069

Measured 1mo ago against content hash 0cba7b1b2892, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.cursor/project-context/deployment.mdc · 70 lines

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
Changes

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.

  1. 1mo ago First seen · 70 lines · 23 tokens per session scan A 0cba7b1b2892

Subscribe to this mod's changes

deployment is a cursor rule published in the GitHub repository sagar25-Code-it/ps3d-cad-studio (0 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 689 once invoked, about $0.0001 per session on Opus 5.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.