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 skills/makigjuro/cloudstack-ai-plugins/add-migrationnpx skills add makigjuro/cloudstack-ai-plugins --skill add-migrationgit clone --depth 1 https://github.com/makigjuro/cloudstack-ai-pluginsWhat 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.00038 | $0.00772 |
| Opus 5 | $0.00019 | $0.00386 |
| Sonnet 5 | $0.00008 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
add-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 2d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add EF Core Migration
Create a new EF Core migration for a microservice's database context.
Arguments
{Name}-- Migration name in PascalCase (e.g.,AddOrdersTable){Service}-- Target microservice (ask if ambiguous)
Configuration
Read cloudstack.json from the project root at the start of execution. Extract:
SERVICES=backend.services[](default: discover fromsrc/*/directories containing.Application/subfolders)SOLUTION=backend.solutionPath(default: find*.slninsrc/)
If cloudstack.json does not exist, auto-detect by scanning the project structure.
Service DbContext Discovery
If a service-to-DbContext mapping is not defined in cloudstack.json, auto-detect by searching for *DbContext.cs files:
grep -rn "class.*DbContext" src/{Service}/**/Infrastructure/ --include="*.cs"
Find the Infrastructure and Host projects:
find src/{Service} -name "*.Infrastructure.csproj" -o -name "*.Host.csproj"
Process
Step 1: Verify Changes
Before creating a migration, check that entity configurations are in place:
# Find the entity configuration
grep -rn "IEntityTypeConfiguration" src/{Service}/
Step 2: Create Migration
Run from the Infrastructure project directory:
dotnet ef migrations add {Name} \
--project src/{Service}/{Service}.Infrastructure \
--startup-project src/{Service}/{Service}.Host \
--output-dir Persistence/Migrations
If the startup project differs from the convention, search for the .Host project:
find src/{Service} -name "*.Host.csproj" -o -name "*.Host" -type d
Step 3: Review Migration
Read the generated migration file and verify:
- Only expected changes are included
- No data loss operations (dropping columns/tables) without user confirmation
- Index names follow conventions
- Foreign keys are correct
# Find the latest migration
ls -t src/{Service}/**/Migrations/*.cs | head -2
Step 4: Apply Migration (Optional)
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.
- 2d ago First seen · 106 lines · 38 tokens per session scan A e011685301eb
add-migration is a skill published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 772 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
azure-mgmt-mongodbatlas-dotnet
Manage MongoDB Atlas Organizations as Azure ARM resources using Azure.ResourceManager.MongoDBAtlas SDK. Use when creating, updating, listing, or deleting MongoDB Atlas organizations through Azure Marketplace integration. This SDK manages the Azure-side organization resource, not Atlas clusters/databases directly.
azure-resource-manager-redis-dotnet
Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) …
dpg-migration
Migration logic for Azure SDK for .NET data-plane libraries migrating from AutoRest/Swagger to TypeSpec-based generation. Uses MCP tools from the generator-agent server for automated deterministic fixes.
csharp-azure-spector-coverage-gaps
Discovers and implements gaps in Spector test coverage for the Azure C# HTTP client emitter. Use when asked to find missing Spector scenarios, add Spector test coverage, or implement a specific Spector spec for the Azure C# emitter. Can also compare coverage between the Azure dashboard and the Standard (TypeSpec core)…
mgmt-review-comment-resolution
Resolve review comments on Azure management-plane .NET SDK PRs. Handles renaming types/properties, changing property types, and other API surface adjustments by updating TypeSpec client.tsp and regenerating.
mpg-migration
Handles Azure SDK for .NET management-plane migrations from AutoRest/Swagger to TypeSpec; use for MPG, mgmt migration, or Azure.ResourceManager. migration requests.