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 skills/nitrocloudofficial/nitrostack/prisma-computenpx skills add nitrocloudofficial/nitrostack --skill prisma-computegit clone --depth 1 https://github.com/nitrocloudofficial/nitrostackWhat 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.00153 | $0.03604 |
| Opus 5 | $0.00077 | $0.01802 |
| Sonnet 5 | $0.00031 | $0.00721 |
| Haiku 4.5 | $0.00015 | $0.00360 |
Grade A, and why
prisma-compute 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- prisma-compute — 95% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prisma Compute
Guide agents through Prisma Compute app creation, deployment, operations, and framework-specific deploy readiness.
Prisma Compute CLI Surface
Use the Prisma Platform CLI for Compute app workflows:
bunx @prisma/cli@latest app deploy --help
bunx @prisma/cli@latest app --help
bunx @prisma/cli@latest build logs --help
bunx create-prisma@latest --help
Use @prisma/cli@latest for Compute app deployment. Use create-prisma@latest for new-project scaffolding.
Send Feedback and Report CLI Issues
The CLI has a built-in feedback channel. Use it whenever a command crashes (UNEXPECTED_ERROR), a failure survives troubleshooting, or the user asks to send feedback to the Prisma team:
bunx @prisma/cli@latest feedback "app deploy crashed: <first error line>"
bunx @prisma/cli@latest feedback "love the deploy flow" --email [email protected]
Crash output points here on its own: --json crash envelopes carry the exact pre-filled command as a recover entry in nextActions (run it verbatim), and human crash output ends with a Tell us what happened: hint. Feedback is anonymous unless --email is passed and attaches only the CLI version, node version, and OS platform/arch. Never include secrets, connection URLs, or user data in the message.
Source-of-Truth Order
Use evidence in this order when deciding what to edit or run:
- The project's generated scripts and config, especially
prisma.compute.ts,compute:deploy, framework config, andpackage.json. - CLI help output from
create-prismaand@prisma/cli. - Local installed package code, generated artifacts, and type definitions.
- Official docs.
When to Apply
Use this skill for:
- Creating a new app that can deploy to Prisma Compute
- Deploying an existing TypeScript app to Prisma Compute
- Creating or updating a typed
prisma.compute.tsdeploy config - Deciding whether a framework is Compute-ready
- Debugging
create-prisma --deploy,compute:deploy, orapp deploy - Managing Compute app logs, deployments, environment variables, and domains, and listing platform branches (
branch list; there are no branch create/remove commands) - Inspecting GitHub/Console build logs and GitHub push-to-deploy status
- Running non-interactive deploys with browser auth, multiple stored workspaces, or Prisma service tokens
- Switching, selecting, listing, or logging out local Prisma Platform workspaces for
@prisma/cli - Installing or updating Prisma skills with
@prisma/cli agent install|update|status - Sending feedback or reporting unresolvable CLI failures with
@prisma/cli feedback - Programmatic deployments with
@prisma/compute-sdkor Management API integrations
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 193 lines · 153 tokens per session scan A 6e64448e6969
prisma-compute is a skill published in the GitHub repository nitrocloudofficial/nitrostack (2,505 stars, last pushed yesterday), licensed Apache-2.0. It adds 153 tokens to every session and 3,604 once invoked, about $0.0008 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-30.
Other skills, from other repositories
bicep-deployment
Author, validate, preview, and ship Azure infrastructure with Bicep the safe way - what-if before deploy, the four deployment scopes, idempotent re-runs, and Well-Architected guardrails. Use when designing or reviewing Bicep templates, choosing a deployment scope, wiring Bicep into GitHub Actions, or teaching IaC…
pinggy-tunnel
Zero-install localhost tunnels over SSH via Pinggy.
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".
aws-solution-architect
../../../engineering-team/skills/aws-solution-architect/SKILL.md.
azure-cloud-architect
../../../engineering-team/skills/azure-cloud-architect/SKILL.md.
doca-bf4-deployment
WARNING: guides potentially IRREVERSIBLE BlueField-4 hardware operations (PLDM firmware burns, ISO reflashes, power cycles, BMC factory resets) that can brick firmware, corrupt boot media, or cause outages — a maintenance window and rollback plan are required, and every mutating step is governed by…