Borrowing it
Nothing to install: this file belongs to chama-x/GroundRules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chama-x/GroundRules/master/.agents/skills/prisma-next/SKILL.mdgit clone --depth 1 https://github.com/chama-x/GroundRulesWrote 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/chama-x/groundrules/prisma-next)<a href="https://agentmods.dev/skills/chama-x/groundrules/prisma-next"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/prisma-next.svg" alt="Measured on agentmods" height="20"></a>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.00233 | $0.01340 |
| Opus 5 | $0.00117 | $0.00670 |
| Sonnet 5 | $0.00047 | $0.00268 |
| Haiku 4.5 | $0.00023 | $0.00134 |
Grade A, and why
prisma-next 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.
This is a copy
100% identical to prisma-next — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
Prisma Next — Router
Edit your data contract. Prisma handles the rest.
This skill exists to disambiguate vague Prisma Next prompts. When the user hasn't yet committed to a specific workflow (e.g. "help me with Prisma Next", "explain how Prisma Next works", "I'm new to PN, where do I start?"), this skill fires and routes them to the right specific skill.
When to Use
- The user has not yet stated a concrete task.
- The user types a meta-question about Prisma Next ("what is Prisma Next?", "how does PN compare to Drizzle/Prisma 7?").
- The user asks for a tour, an overview, or a starting point.
When Not to Use
- The user named a workflow — use the matching skill directly:
- Setting up a new project or adopting an existing DB →
prisma-next-quickstart. - Editing the schema, adding a model, changing a field →
prisma-next-contract. - Authoring a migration, fixing a planner error →
prisma-next-migrations. - Reviewing what's about to run on merge, handling concurrent migrations →
prisma-next-migration-review. - Writing a query →
prisma-next-queries. - Supabase — RLS policies, role binding (
asUser/asAnon/asServiceRole),auth.usersFKs,@prisma-next/extension-supabase→prisma-next-supabase. - Wiring
db.ts, middleware, environment config →prisma-next-runtime. - Build-system / dev-server plugin (Vite, Next.js, …) →
prisma-next-build. - A specific error code or symptom →
prisma-next-debug. - Reporting a bug or filing a feature request against Prisma Next →
prisma-next-feedback.
- Setting up a new project or adopting an existing DB →
Routing rules
If the user's prompt clearly matches one of the workflow skills, route there directly without asking.
Otherwise, ask one disambiguating question. Pick from:
- "Are you new to Prisma Next and asking what you can do with it, or where to start?" (and any "what can I do with Prisma Next?" / "I just ran createprisma" variant) →
prisma-next-quickstart(first-touch orientation path). - "Do you want to set up a new Prisma Next project, or wire it into an existing database?" →
prisma-next-quickstart. - "Do you want to edit your data contract (add a model / field / relation), or work with the database (migrations, queries)?" →
prisma-next-contractvs the others. - "Is this about authoring a migration, or about reviewing what's going to run on deploy?" →
prisma-next-migrationsvsprisma-next-migration-review. - "Is this about wiring Prisma Next into your build tool (Vite / Next.js / …), or about wiring
db.tsand middleware at runtime?" →prisma-next-buildvsprisma-next-runtime. - "What error or symptom are you seeing?" →
prisma-next-debug. - "Do you want to report this as a bug to the Prisma Next team, or is this a feature request?" →
prisma-next-feedback.
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 · 233 tokens per session scan A 1020bcfb4723
prisma-next is a skill published in the GitHub repository chama-x/GroundRules (5 stars, last pushed 23d ago), licensed MIT. It adds 233 tokens to every session and 1,340 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to prisma-next, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
embeddings
Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support. 75x faster with agentic-flow integration. Use when: semantic search, pattern matching, similarity queries, knowledge retrieval. Skip when: exact text matching, simple lookups, no semantic understanding needed.
notion-tool
Notion integration tool for searching, reading, creating, and updating pages and databases via the API. Use when: editing Notion pages, adding database rows, or searching a workspace.
AgentDB Performance Optimization
Optimize AgentDB performance with quantization (4-32x memory reduction), HNSW indexing (150x faster search), caching, and batch operations. Use when optimizing memory usage, improving search speed, or scaling to millions of vectors.
AgentDB Vector Search
Implement semantic vector search with AgentDB for intelligent document retrieval, similarity matching, and context-aware querying. Use when building RAG systems, semantic search engines, or intelligent knowledge bases.
V3 Memory Unification
Unify 6+ memory systems into AgentDB with HNSW indexing for 150x-12,500x search improvements. Implements ADR-006 (Unified Memory Service) and ADR-009 (Hybrid Memory Backend).
database-verification
Shell-based database connectivity and integrity checks. Verifies that databases are reachable, schemas match expectations, and data integrity constraints hold.