new-entity

new-entity is a command for GitHub Copilot from srnichols/plan-forge. It costs 24 tokens per session (782 once invoked), scanned A, original, MIT.

A command that creates a database entity across the application: a SQL migration, data-access repository, service, DTO, API controller, and tests. A migration is a tracked database change used to create or alter tables safely.

In plain words
What is it for?
Use it to add a new record type with PostgreSQL-style IDs and timestamps, repository and service operations, API endpoints, validation, and tests.
Why use it?
It avoids wiring only part of a new feature and encourages parameterized SQL, which prevents user input from being treated as SQL code.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt. Also seen: agent in frontmatter.

Good fit Use it to add a new record type with PostgreSQL-style IDs and timestamps, repository and service operations, API endpoints, validation, and tests.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/srnichols/plan-forge/new-entity
Install

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.

Clone the repo
git clone --depth 1 https://github.com/srnichols/plan-forge

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for new-entity

README.md
[![agentmods](https://agentmods.dev/badge/commands/srnichols/plan-forge/new-entity.svg)](https://agentmods.dev/commands/srnichols/plan-forge/new-entity)
Your own site
<a href="https://agentmods.dev/commands/srnichols/plan-forge/new-entity"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-entity.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 782 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00782
Opus 5 $0.00012 $0.00391
Sonnet 5 $0.00005 $0.00156
Haiku 4.5 $0.00002 $0.00078

Measured today against content hash c6ae5cd621f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

new-entity 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 today.

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.

presets/dotnet/.github/prompts/new-entity.prompt.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create New Database Entity

Scaffold a complete entity from database to API following the layered architecture.

Required Steps

  1. Create migration SQL at Database/migrations/YYYYMMDD_add_{entity_name}.sql:

    • Table with id UUID PRIMARY KEY DEFAULT gen_random_uuid()
    • created_at TIMESTAMPTZ DEFAULT NOW(), updated_at TIMESTAMPTZ DEFAULT NOW()
    • IF NOT EXISTS guards for idempotency
    • Appropriate indexes on frequently queried columns
  2. Create DTO at src/Models/{EntityName}Dto.cs:

    • Use record type for immutable DTOs
    • PascalCase properties mapping to snake_case columns (if applicable)
  3. Create repository interface at src/Repositories/I{EntityName}Repository.cs

  4. Create repository at src/Repositories/{EntityName}Repository.cs:

    • Use the project's data access pattern (Dapper or EF Core)
    • Parameterized queries only — NEVER string interpolation in SQL
    • CancellationToken on all async methods
  5. Create service interface at src/Services/I{EntityName}Service.cs

  6. Create service at src/Services/{EntityName}Service.cs:

    • ALL business logic lives here (not controllers, not repositories)
    • Input validation, duplicate checks, authorization
    • CancellationToken on all async methods
  7. Create controller at src/Controllers/{EntityName}Controller.cs:

    • [ApiController] with [Route("api/[controller]")]
    • [Authorize] at class level
    • Delegates ALL work to the service layer
    • Returns ProblemDetails for errors
  8. Register DI in Program.cs:

    builder.Services.AddScoped<I{EntityName}Repository, {EntityName}Repository>();
    builder.Services.AddScoped<I{EntityName}Service, {EntityName}Service>();
    
  9. Create tests — TDD preferred:

    • Unit test for service logic with mocked repository
    • Integration test for repository with real database
  10. Update documentation if schema changed

Naming Conventions

  • Database columns: snake_case (e.g., created_at)
  • DTO properties: PascalCase (e.g., CreatedAt)
  • Always use explicit column aliases in SELECT: SELECT created_at AS CreatedAt

Read the full file on GitHub · 87 lines

Changes

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.

  1. today First seen · 87 lines · 24 tokens per session scan A c6ae5cd621f5

Subscribe to this mod's changes

new-entity is a command published in the GitHub repository srnichols/plan-forge (5 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 782 once invoked, about $0.0001 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-09-08.