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/ahmedawan-oracle/claude-code-pluginsWrote 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/ahmedawan-oracle/claude-code-plugins/migrate-catalog)<a href="https://agentmods.dev/commands/ahmedawan-oracle/claude-code-plugins/migrate-catalog"><img src="https://agentmods.dev/badge/commands/ahmedawan-oracle/claude-code-plugins/migrate-catalog/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/ahmedawan-oracle/claude-code-plugins/migrate-catalog"><img src="https://agentmods.dev/badge/commands/ahmedawan-oracle/claude-code-plugins/migrate-catalog.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.00041 | $0.00672 |
| Opus 5.5 | $0.00016 | $0.00269 |
| Sonnet 5.5 | $0.00008 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
migrate-catalog 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 2mo 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/migrate-catalog — guided catalog migration
Walk the user through extracting Unity Catalog / HMS metadata from Databricks, previewing the rewritten DDL, and replaying it on AIDP.
Workflow
- Confirm prereqs — invoke
aidp-migrator-bootstrap. Especially checkDATABRICKS_HOST+DATABRICKS_TOKENare set (catalog extract needs them). - Confirm scope — ask which catalogs / schemas the user wants to migrate. Default to "everything in this catalog" but accept a filter list.
- Confirm bucket mapping — if any external tables have
s3://locations, the bucket-map config must exist. Route toaidp-bucket-mappingif missing. - Stage 1: extract —
extract_catalog_databricks.py→reports/catalog_pack.json. Show the table count. - Stage 2 dry-run: rewrite preview —
migrate_catalog.py --dry-run. Surface:- Total CREATE SCHEMA statements
- Total CREATE TABLE statements
- Any rejections (MV / streaming / unsupported)
- Any bucket-map misses Ask the user "ready to replay on the cluster?"
- Stage 2 replay —
migrate_catalog.py(no--dry-run). Surface per-chunk status. - Verify — for each migrated schema, run
SHOW TABLES IN default.<schema>and surface the count. Compare to extract.
Args
$ARGUMENTS
If $ARGUMENTS provides <catalog> or <catalog>:<schema> filters, use them; else ask.
Checkpoints
[Phase 1/4] Extracted N catalogs, M schemas, K tables → reports/catalog_pack.json
[Phase 2/4] Dry-run: would create N schemas + M tables. Rejected: K MVs, J streaming tables.
About to run live DDL replay — proceed? (y/N)
[Phase 3/4] Replayed in 4 chunks of 25 statements each. All chunks committed.
[Phase 4/4] Verify: SHOW TABLES across each schema. Discrepancies: 0
When to stop
- User aborts at the dry-run checkpoint.
- Bucket-map is missing buckets — fix first via
aidp-bucket-mapping. - Dry-run shows >10% rejected (MVs / streaming) — likely a structural mismatch; review with the user before proceeding.
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.
- 2mo ago First seen · 50 lines · 41 tokens per session scan A f31d8ef19350
migrate-catalog is a command published in the GitHub repository ahmedawan-oracle/claude-code-plugins (4 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 672 once invoked, about $0.0002 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.
migrate-catalog compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| migrate-catalogahmedawan-oracle/claude-code-plugins | Command | 4 | 3mo ago | MIT | A | 41 | Claude Code |
| initfcakyon/claude-codex-settings | Command | 1.2k | today | Apache-2.0 | A | 0 | Claude Code |
| securityajitpratap0/GoSQLX | Command | 124 | today | Apache-2.0 | A | 21 | Claude Code |
| database-setupimsaif/design-with-claude | Command | 11 | 3d ago | MIT | A | 36 | Claude Code |
| new-migrationRaNDoM6913/claude-code-superkit | Command | 3 | today | MIT | A | 22 | Claude Code |
| json.batch_getstratalab/strata-core | Command | 5 | 1mo ago | Apache-2.0 | A | 0 | Claude Code |
| json.index.dropstratalab/strata-core | Command | 5 | 1mo ago | Apache-2.0 | A | 0 | Claude Code |