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 instructions/thesethrose/copilot-skills/prismagit clone --depth 1 https://github.com/TheSethRose/Copilot-SkillsWrote 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/instructions/thesethrose/copilot-skills/prisma)<a href="https://agentmods.dev/instructions/thesethrose/copilot-skills/prisma"><img src="https://agentmods.dev/badge/instructions/thesethrose/copilot-skills/prisma.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 | $0.01291 | $0.01291 |
| Opus 5 | $0.00646 | $0.00646 |
| Sonnet 5 | $0.00258 | $0.00258 |
| Haiku 4.5 | $0.00129 | $0.00129 |
Grade A, and why
Copilot-Skills prisma.instructions.md 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 4d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prisma Instructions
Auto-loaded when: Working with files matching: **/prisma/**, **/*.prisma, **/*.ts, **/*.js, **/schema.prisma
Default Behaviors
When working with Prisma:
- Use Prisma Schema First: Define your data model in
prisma/schema.prisma - Generate Client: Always run
npx prisma generateafter schema changes - Type Safety: Leverage generated types from Prisma Client
- Migrations: Use
npx prisma migratefor schema changes - Testing: Use
@prisma/internalsfor testing databases - Async Patterns: Always use
.disconnect()after operations
Common Workflows
Schema Definition
// prisma/schema.prisma
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
}
model User {
id Int @id @default(autoincrement())
email String @unique
name String?
posts Post[]
}
model Post {
id Int @id @default(autoincrement())
title String
authorId Int
author User @relation(fields: [authorId], references: [id])
}
Basic CRUD Operations
import { PrismaClient } from "@prisma/client";
const prisma = new PrismaClient();
// Create
const user = await prisma.user.create({
data: { email: "[email protected]", name: "John" }
});
// Read
const foundUser = await prisma.user.findUnique({
where: { id: 1 }
});
// Update
const updated = await prisma.user.update({
where: { id: 1 },
data: { name: "Jane" }
});
// Delete
await prisma.user.delete({ where: { id: 1 } });
await prisma.$disconnect();
With Relations
// Create with nested relations
const user = await prisma.user.create({
data: {
email: "[email protected]",
posts: {
create: [
{ title: "First Post" },
{ title: "Second Post" }
]
}
},
include: { posts: true }
});
// Query with relations
const userWithPosts = await prisma.user.findUnique({
where: { id: 1 },
include: {
posts: {
where: { published: true },
orderBy: { createdAt: "desc" }
}
}
});
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.
- 4d ago First seen · 236 lines · 1,291 tokens per session scan A 4ecc667a0a4b
Copilot-Skills prisma.instructions.md is an instructions file published in the GitHub repository TheSethRose/Copilot-Skills (3 stars, last pushed 8mo ago), licensed MIT. It adds 1,291 tokens to every session, about $0.0065 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 instructions, from other repositories
copilot copilot-instructions.md
Copilot instructions for navikt/copilot, covering copilot instructions for navikt/copilot, repository overview, nav development standards, nav principles and nav tech stack.
copilot AGENTS.md
AGENTS.md instructions for navikt/copilot, covering agents.md for navikt/copilot, what this repo is, efficiency rule, standard commands and conventions.
rosetta schema-roundtrip-compat.instructions.md
Instructions for tikoci/rosetta, a project described as: MCP Server with RouterOS docs + commands + products + changelogs, using SQLite-as-RAG, sourced from MikroTik.
github-copilot-superpowers copilot-agent.instructions.md
Instructions for kasuken/github-copilot-superpowers, covering copilot agent instructions, 🎯 instruction hierarchy, 📋 execution order vs priority, execution order (workflow sequence) and ⛔ mandatory response template (every request).
github-copilot-superpowers subagents.instructions.md
Instructions for kasuken/github-copilot-superpowers, covering subagent instructions (ssot), terminology, agent role: orchestrator only, ⚠️ absolute rules (non-negotiable) and mcp delegation rules.
copilot-guide copilot-instructions.md
Instructions for nishanil/copilot-guide, covering copilot-guide — copilot instructions, what this repo is, contribution conventions, style rules and what not to change.