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.
git clone --depth 1 https://github.com/fusengine/agentsWrote 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/commands/fusengine/agents/prisma-optimize)<a href="https://agentmods.dev/commands/fusengine/agents/prisma-optimize"><img src="https://agentmods.dev/badge/commands/fusengine/agents/prisma-optimize/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.
<a href="https://agentmods.dev/commands/fusengine/agents/prisma-optimize"><img src="https://agentmods.dev/badge/commands/fusengine/agents/prisma-optimize.svg" alt="Reviewed on agentmods" width="80" 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.00022 | $0.01213 |
| Opus 5.5 | $0.00009 | $0.00485 |
| Sonnet 5.5 | $0.00004 | $0.00243 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
prisma-optimize 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.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚀 Prisma Query Optimization
Automatically analyzes and optimizes your Prisma queries by detecting performance issues, N+1 queries, missing indexes, and proposing solutions based on official Prisma documentation 2024-2025.
Phase 1: ANALYZE 🔍
Step 1.1: Fetch Official Documentation
Use research-expert to fetch official Prisma documentation
Goals:
- Obtain latest Prisma optimization documentation
- Verify recommended patterns for Prisma Optimize
- Identify best practices 2024-2025
Actions:
- Search for Prisma Optimize, Query Optimization, Performance documentation
- Verify
@prisma/extension-optimizeextension APIs - Confirm patterns to avoid N+1 queries
Query Focus:
"Prisma Optimize best practices, N+1 detection, query optimization patterns,
index recommendations, select vs include, relationLoadStrategy"
Deliverable: Prisma optimization guide with verified methods
Step 1.2: Explore Prisma Codebase
Use explore-codebase to analyze existing Prisma setup
Goals:
- Locate Prisma files (schema.prisma, client queries)
- Identify existing query patterns
- Detect potential performance issues
Actions:
- Search for
schema.prisma,*.prismafiles - Analyze files containing
prisma.to find queries - Map relations and data access patterns
Deliverable: Map of Prisma queries and potential issues
Phase 2: DETECT ISSUES 🎯
Automated Problem Detection
After exploration, systematically analyze:
🚨 Issue 1: N+1 Queries
Detected Pattern:
// ❌ Anti-pattern detected
const users = await prisma.user.findMany()
users.forEach(async (user) => {
const posts = await prisma.post.findMany({ where: { authorId: user.id } })
})
Recommended Solutions:
-
include(Simple):const users = await prisma.user.findMany({ include: { posts: true } }) -
relationLoadStrategy: "join"(Performant):const users = await prisma.user.findMany({ relationLoadStrategy: "join", include: { posts: true } })
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.
- 1mo ago First seen · 243 lines · 22 tokens per session scan A 3f627c3fd928
prisma-optimize is a command published in the GitHub repository fusengine/agents (31 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 1,213 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-30.
Other commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
archetype-impact
Scan the current workspace for all references to a given archetype across templates (.oet / .t.json source, .opt compiled) and AQL files, producing an impact table useful before editing a widely-reused archetype.
db-audit
Audit database schema and queries for performance and design issues.
migrate
Generate database migration files for schema changes.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.