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/thapaliyabikendra/ai-artifactsWrote 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/thapaliyabikendra/ai-artifacts/entity)<a href="https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/entity"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/entity/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/thapaliyabikendra/ai-artifacts/entity"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/entity.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.00020 | $0.01575 |
| Opus 5.5 | $0.00008 | $0.00630 |
| Sonnet 5.5 | $0.00004 | $0.00315 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
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 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Entity Command
Scaffold a complete ABP Framework entity with all layers.
Arguments: $ARGUMENTS
Pre-flight
Project: !basename $(pwd)
Domain: !find api/src -maxdepth 1 -type d -name "*Domain" ! -name "*Shared" 2>/dev/null | head -1
Application: !find api/src -maxdepth 1 -type d -name "*Application" ! -name "*Contracts" 2>/dev/null | head -1
Required context:
- Read
CLAUDE.mdfor project conventions - Read
docs/architecture/README.mdfor project paths
Mode Selection
| Mode | Stages | Speed | Use When |
|---|---|---|---|
| (default) | Full scaffolding with docs | ~3 min | Complete feature setup |
--fast |
Code only, no docs | ~2 min | Quick CRUD, prototyping |
--minimal |
Entity + DTO only | ~1 min | Minimal scaffolding |
Workflow
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ 1.Entity │ → │ 2. DTOs │ → │ 3.Service│ → │ 4.Valid- │ → │ 5.DbCtx │
│ (Domain) │ │(Contract)│ │ (App) │ │ ator │ │ + Perm │
└──────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘
Execution
Use Task tool with subagent_type="abp-developer":
Generate complete ABP entity scaffolding for: {EntityName}
Properties: {properties or prompt for them}
Audit: {audit-level: full|basic|none, default: full}
Mode: {default|fast|minimal}
Skills: Apply abp-framework-patterns, abp-entity-patterns, abp-service-patterns, efcore-patterns, fluentvalidation-patterns
## Output Files
### 1. Domain Layer: Entity
api/src/{Project}.Domain/{EntityPlural}/{Entity}.cs
- Inherit FullAuditedAggregateRoot<Guid>
- Private setters with SetXxx() methods
- Private parameterless constructor
- Validation in setters using Check.NotNullOrWhiteSpace
### 2. Application.Contracts: DTOs + Interface
api/src/{Project}.Application.Contracts/{EntityPlural}/
- {Entity}Dto.cs
- CreateUpdate{Entity}Dto.cs
- Get{Entity}ListInput.cs (extends PagedAndSortedResultRequestDto)
- I{Entity}AppService.cs
### 3. Application: AppService + Validator
api/src/{Project}.Application/{EntityPlural}/
- {Entity}AppService.cs (CRUD with [Authorize] attributes)
- CreateUpdate{Entity}DtoValidator.cs (FluentValidation)
### 4. EntityFrameworkCore: Configuration
api/src/{Project}.EntityFrameworkCore/{EntityPlural}/
- {Entity}Configuration.cs (IEntityTypeConfiguration)
- Add DbSet<{Entity}> to DbContext
### 5. Permissions (edit existing)
- Add constants to {Project}Permissions.cs
- Register in PermissionDefinitionProvider.cs
### 6. Mapperly (edit existing)
- Add mapping methods to ApplicationMappers.cs
## Build Verification
Run: dotnet build api/*.slnx
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 · 177 lines · 20 tokens per session scan A 2b9e5a6359f2
entity is a command published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 1,575 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
init
Initialize configurations for Supabase local development.
toh-connect
Connect app to Supabase backend with schema and RLS policies.
model-create
Create a new Django model following best-practice conventions.
crud
Generates a complete CRUD domain in the house pattern (Express + Prisma, multi-tenant).
services
Manage the connect service registry. Register API services and database connections, store credentials, set read-only vs write access, manage the destination allowlist, and report trust status.
p3-data-model
Designs the Data Model with entities and relationships as well as the API design with interface specification. The result is DATAMODEL.md and APISPEC.md as the binding foundation for implementation.