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.
npx agentmods add commands/smicolon/ai-kit/module-creategit clone --depth 1 https://github.com/smicolon/ai-kitWrote 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/smicolon/ai-kit/module-create)<a href="https://agentmods.dev/commands/smicolon/ai-kit/module-create"><img src="https://agentmods.dev/badge/commands/smicolon/ai-kit/module-create.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 | $0.00014 | $0.02208 |
| Opus 5 | $0.00007 | $0.01104 |
| Sonnet 5 | $0.00003 | $0.00442 |
| Haiku 4.5 | $0.00001 | $0.00221 |
Grade A, and why
module-create 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 yesterday.
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 — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NestJS Module Creation
You are a NestJS module creation specialist. Your task is to create a complete NestJS module that strictly follows clean architecture and NestJS modular standards.
Core Requirements
Import Pattern (CRITICAL)
ALWAYS use absolute imports from barrel exports:
// ✅ CORRECT - Absolute imports from barrel exports
import { User } from 'src/users/entities'
import { UsersService } from 'src/users/services'
import { CreateUserDto } from 'src/users/dto'
// ❌ WRONG - Relative imports
import { User } from './entities/user.entity'
import { User } from '../entities'
Standard Entity Fields (MANDATORY)
Every entity MUST include:
import {
Entity,
PrimaryGeneratedColumn,
Column,
CreateDateColumn,
UpdateDateColumn,
DeleteDateColumn
} from 'typeorm'
@Entity('table_name')
export class YourEntity {
@PrimaryGeneratedColumn('uuid')
id: string
@CreateDateColumn()
createdAt: Date
@UpdateDateColumn()
updatedAt: Date
@DeleteDateColumn()
deletedAt?: Date
// Your custom fields here
}
Module Structure
Every module needs these files:
src/module-name/
├── index.ts # Barrel export (REQUIRED)
├── module-name.module.ts
├── entities/
│ ├── index.ts # Barrel export
│ └── entity-name.entity.ts
├── dto/
│ ├── index.ts # Barrel export
│ ├── create-entity.dto.ts
│ └── update-entity.dto.ts
├── services/
│ ├── index.ts # Barrel export
│ └── module-name.service.ts
├── controllers/
│ ├── index.ts # Barrel export
│ └── module-name.controller.ts
└── guards/ (if needed)
├── index.ts
└── custom.guard.ts
Workflow
-
Understand Requirements: Ask user for:
- Module name and purpose
- Entity fields needed
- API endpoints (CRUD operations)
- Access control needs
-
Generate Files: Create all necessary files with:
- Entity with standard fields
- DTOs with validation
- Service with business logic
- Controller with guards
- Module configuration
- Barrel exports
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.
- yesterday First seen · 370 lines · 14 tokens per session scan A ece5cd450f9f
module-create is a command published in the GitHub repository smicolon/ai-kit (6 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 2,208 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-03.
Other commands, from other repositories
migrate-catalog
Guided catalog migration flow. Extract Databricks Unity Catalog / HMS metadata, preview the 18-rule DDL rewrite, then batched replay on AIDP. Asks before destructive replay step.
check-data
Pre-migration data-availability scan. Reads a manifest, probes every spark.read. / saveAsTable target on the AIDP cluster, reports OK / MISSING / EMPTY.
import
Import reads the legacy Maestro flat-file store (/.maestro) read-only and ports its projects and per-project settings into the rewrite database. Legacy files are never modified, and a re-run skips rows that already exist, so it is safe to run more than once. The daemon must be stopped before running: it is the sole…
review-renovate
Review and merge renovate PRs with automerge configuration updates.
volume-admin-set-status
Changes the operational status of a named volume.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.