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/migration)<a href="https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/migration"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/migration/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/migration"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/migration.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.00010 | $0.00994 |
| Opus 5.5 | $0.00004 | $0.00398 |
| Sonnet 5.5 | $0.00002 | $0.00199 |
| Haiku 4.5 | $0.00001 | $0.00099 |
Grade A, and why
migration 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Migration Command
Generate and optionally apply EF Core migrations for ABP Framework.
Arguments: $ARGUMENTS
Pre-flight
Project: !basename $(pwd)
EF Core Project: !find api/src -maxdepth 1 -type d -name "*EntityFrameworkCore" 2>/dev/null | head -1
DbMigrator: !find api/src -maxdepth 1 -type d -name "*DbMigrator" 2>/dev/null | head -1
Workflow
┌──────────────┐ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ 1. Detect │ → │ 2. Generate │ → │ 3. Review │ → │ 4. Apply │
│ Changes │ │ Migration │ │ SQL │ │ (optional) │
└──────────────┘ └──────────────┘ └──────────────┘ └──────────────┘
Execution
Step 1: Detect Pending Changes
# Locate projects dynamically
EF_PROJECT=$(find api/src -maxdepth 1 -type d -name "*EntityFrameworkCore" | head -1)
MIGRATOR=$(find api/src -maxdepth 1 -type d -name "*DbMigrator" | head -1)
cd "$EF_PROJECT"
dotnet ef dbcontext info --startup-project "../$(basename $MIGRATOR)"
Review DbContext for:
- New DbSet<> properties
- Modified entity configurations
- New relationships
Step 2: Generate Migration
cd "$EF_PROJECT"
dotnet ef migrations add {migration-name} \
--startup-project "../$(basename $MIGRATOR)" \
--output-dir Migrations
Step 3: Review Generated Migration
After generation, review the migration file:
- Open
Migrations/{timestamp}_{migration-name}.cs - Check
Up()method for:- Table creation with correct columns
- Index definitions
- Foreign key constraints
- Default values
- Check
Down()method for proper rollback - Verify no data loss operations
Review Checklist:
- Column types match entity properties
- Required columns have
nullable: false - String columns have
maxLengthconstraints - Indexes defined for query patterns
- Foreign keys have appropriate delete behavior
- No accidental data dropping operations
Step 4: Apply Migration (if --apply)
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 · 146 lines · 10 tokens per session scan A 837edbfd9faa
migration is a command published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 994 once invoked, about $0.0000 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.
security
Scan a SQL string, .sql file, or SQL-building source file for injection risks with GoSQLX.
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.
new-migration
Scaffold a new database migration file pair (up + down) with auto-detection of migration tool and numbering.
json.batch_get
Read multiple JSON values by document and path.
json.batch_delete
Delete multiple JSON documents or paths in one itemwise batch.