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/hmake98/nestjs-starterWrote 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/hmake98/nestjs-starter/gen-prisma-model)<a href="https://agentmods.dev/commands/hmake98/nestjs-starter/gen-prisma-model"><img src="https://agentmods.dev/badge/commands/hmake98/nestjs-starter/gen-prisma-model/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/hmake98/nestjs-starter/gen-prisma-model"><img src="https://agentmods.dev/badge/commands/hmake98/nestjs-starter/gen-prisma-model.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.00000 | $0.00448 |
| Opus 5.5 | $0.00000 | $0.00179 |
| Sonnet 5.5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
gen-prisma-model 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 2mo 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.
What it actually says
Add a new Prisma model to this codebase: $ARGUMENTS
Read these files first:
prisma/schema.prisma— existing schema conventionssrc/common/database/database.module.ts— where to register the new repositorysrc/common/database/interfaces/user.interface.ts— interface patternsrc/common/database/repositories/user.repository.ts— repository pattern
Follow these conventions from the existing schema:
- Field names in camelCase, mapped to snake_case with
@map("snake_case") - All models have:
id String @id @default(uuid()),createdAt,updatedAt @updatedAt,deletedAt DateTime?for soft delete - Table names use
@@map("plural_snake_case") - Enums defined in the schema and re-exported from
src/common/database/enums/
Do all of the following:
-
Add the model to
prisma/schema.prismafollowing the conventions above -
Create
src/common/database/interfaces/<name>.interface.tsimport type { <Name> } from '@prisma/client'; export type <Name>Entity = <Name>; export interface Create<Name>Input { ... } export interface Update<Name>Input { ... } -
Create
src/common/database/repositories/<name>.repository.ts- Standard methods:
findById,findAll(with optional pagination),existsById,create,update,softDelete hardDeleteByIdfor test cleanup
- Standard methods:
-
Update
src/common/database/database.module.ts— add the new repository to bothprovidersandexports -
Run the migration command after schema changes:
npm run db:generateThen remind me to run:
npm run db:migrate -- --name <descriptive_migration_name>
If any new enum is needed, also create src/common/database/enums/<name>.enum.ts re-exporting from @prisma/client.
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.
- 2mo ago First seen · 43 lines · 0 tokens per session scan A 61b35f78b2e0
gen-prisma-model is a command published in the GitHub repository hmake98/nestjs-starter (64 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 448 tokens. 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.
gen-prisma-model compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| gen-prisma-modelhmake98/nestjs-starter | Command | 64 | 5mo ago | MIT | A | 0 | Claude Code |
| validate-auth-schemakriasoft/react-starter-kit | Command | 24k | 5d ago | MIT | A | 0 | Claude Code |
| index-managementupstash/redis-js | Command | 983 | yesterday | MIT | A | 0 | Claude Code |
| aliasesupstash/redis-js | Command | 983 | yesterday | MIT | A | 0 | Claude Code |
| db-migrationYuDefine/nuxt-supabase-starter | Command | 44 | yesterday | MIT | A | 12 | Claude Code |
| unfreezeYuDefine/nuxt-supabase-starter | Command | 44 | yesterday | MIT | A | 11 | Claude Code |
| guardYuDefine/nuxt-supabase-starter | Command | 44 | yesterday | MIT | C | 9 | Claude Code |