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/srnichols/plan-forgeWrote 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/srnichols/plan-forge/new-entity)<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>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.00024 | $0.00782 |
| Opus 5 | $0.00012 | $0.00391 |
| Sonnet 5 | $0.00005 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
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.
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
-
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 EXISTSguards for idempotency- Appropriate indexes on frequently queried columns
- Table with
-
Create DTO at
src/Models/{EntityName}Dto.cs:- Use
recordtype for immutable DTOs - PascalCase properties mapping to snake_case columns (if applicable)
- Use
-
Create repository interface at
src/Repositories/I{EntityName}Repository.cs -
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
CancellationTokenon all async methods
-
Create service interface at
src/Services/I{EntityName}Service.cs -
Create service at
src/Services/{EntityName}Service.cs:- ALL business logic lives here (not controllers, not repositories)
- Input validation, duplicate checks, authorization
CancellationTokenon all async methods
-
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
ProblemDetailsfor errors
-
Register DI in
Program.cs:builder.Services.AddScoped<I{EntityName}Repository, {EntityName}Repository>(); builder.Services.AddScoped<I{EntityName}Service, {EntityName}Service>(); -
Create tests — TDD preferred:
- Unit test for service logic with mocked repository
- Integration test for repository with real database
-
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
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.
- today First seen · 87 lines · 24 tokens per session scan A c6ae5cd621f5
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.
Other commands, from other repositories
cap-setup-wizard
Interactive guide for setting up new CAP projects with framework and database selection.
db-auth
A deployment command for connecting a web app to Neon, a hosted PostgreSQL database, and Clerk, a service for user sign-in and account management.
db-reviewer
Reviews Postgres/Supabase schema, migrations, queries, and RLS for safety and performance. Use when DB code changes, before applying a migration, or inside /...
migration-safety
Generate safe, reversible Postgres/Supabase migrations using the expand→backfill→contract pattern, avoiding locks and data loss. Use when altering schema, ad...
query-optimizer
Diagnose and fix slow Postgres queries using EXPLAIN ANALYZE, index suggestions, and N+1 detection. Use when a query is slow, a page is slow because of the D...
rls-policy
Write and test Supabase/Postgres Row-Level Security policies so users can only access their own rows. Use when a table holds user data, when enabling RLS, or...