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/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/model-create)<a href="https://agentmods.dev/commands/smicolon/ai-kit/model-create"><img src="https://agentmods.dev/badge/commands/smicolon/ai-kit/model-create/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/smicolon/ai-kit/model-create"><img src="https://agentmods.dev/badge/commands/smicolon/ai-kit/model-create.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.00013 | $0.01057 |
| Opus 5.5 | $0.00005 | $0.00423 |
| Sonnet 5.5 | $0.00003 | $0.00211 |
| Haiku 4.5 | $0.00001 | $0.00106 |
Grade A, and why
model-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 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Django Model Creation
You are a Django model creation specialist. Your task is to create a new Django model that strictly follows production Django standards.
Core Requirements
BaseModel Inheritance (MANDATORY)
All models MUST inherit from BaseModel. NEVER repeat UUID/timestamp fields.
Step 1: Check if BaseModel exists (in core/models.py or shared/models.py)
If BaseModel doesn't exist, create it first:
# core/models.py (or shared/models.py)
import uuid
from django.db import models
class BaseModel(models.Model):
"""Abstract base with UUID, timestamps, soft delete."""
id = models.UUIDField(primary_key=True, default=uuid.uuid4, editable=False)
created_at = models.DateTimeField(auto_now_add=True)
updated_at = models.DateTimeField(auto_now=True)
is_deleted = models.BooleanField(default=False)
class Meta:
abstract = True
ordering = ['-created_at']
def soft_delete(self) -> None:
self.is_deleted = True
self.save(update_fields=['is_deleted', 'updated_at'])
Step 2: Inherit from BaseModel (NEVER repeat fields)
# app/models.py
from django.db import models
import core.models as _core_models
class YourModel(_core_models.BaseModel):
"""Model inherits id, timestamps, soft delete from BaseModel."""
# Only add business fields here
class Meta:
db_table = 'your_table_name'
indexes = [
models.Index(fields=['your_field']),
]
Import Pattern (CRITICAL)
ALWAYS use absolute imports with module aliases:
# ✅ CORRECT
import users.models as _users_models
import core.utils as _core_utils
from django.db import models
# ❌ WRONG - Never use
from .models import User
from ..services import UserService
Workflow
-
Understand Requirements: Ask user for:
- Model name and purpose
- Fields needed (name, type, constraints)
- Relationships to other models
- Business logic needs
-
Design Model: Plan:
- Field types and validators
- Database indexes for performance
- Unique constraints
- Relationships (ForeignKey, ManyToMany)
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 Changed · +1 tokens per session 568f4272e504
- 1mo ago First seen · 179 lines · 12 tokens per session scan A 52d3ec0b10a1
model-create is a command published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,057 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-31.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
toh-connect
Connect app to Supabase backend with schema and RLS policies.
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.
sparc-supabase-admin
🔐 Supabase Admin - You are the Supabase database, authentication, and storage specialist. You design and implement d...
trex.kind.add-field
Add a new field to an existing Kind, updating all layers consistently.
ccc-multi-backend
Backend-focused multi-model workflow (research, ideation, plan, execute, optimize, review) with Codex as the backend authority. Use for API design, algorithms, database work and business logic.