Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ahmedawan-oracle/claude-code-plugins/plugin install oracle-ai-data-platform-workbench-databricks-migratorWrote 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/check-data)<a href="https://agentmods.dev/commands/ahmedawan-oracle/claude-code-plugins/check-data"><img src="https://agentmods.dev/badge/commands/ahmedawan-oracle/claude-code-plugins/check-data/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/check-data"><img src="https://agentmods.dev/badge/commands/ahmedawan-oracle/claude-code-plugins/check-data.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.00037 | $0.00518 |
| Opus 5.5 | $0.00015 | $0.00207 |
| Sonnet 5.5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
check-data 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.
What it actually says
/check-data — pre-migration scan
Light wrapper over aidp-check-data. Use before any aidp-migrate-job run.
Workflow
- Find an existing manifest at
reports/<job>_manifest.json. If none, ask the user to build one via/migrate-jobPhase 1, OR runaidp-build-dag. - Invoke
${CLAUDE_PLUGIN_ROOT}/engine/scripts/check_data_availability.py(or_for_workflow.pyif the manifest came from a Databricks Job ID). - Output a 3-section summary: TABLES (OK / MISSING / EMPTY), PATHS (same), and a remediation tip per category.
Args
$ARGUMENTS
If $ARGUMENTS names a manifest file or job name, use it; else infer from the most recent reports/<job>_manifest.json.
Output template
== Data availability for <MyJob> ==
TABLES — 23 total
OK 21
MISSING 1 → '<catalog>.<schema>.<table_b>' — run /migrate-catalog or create manually
EMPTY 1 → '<catalog>.<schema>.<table_c>' (0 rows; data backfill needed)
PATHS — 8 total
OK 7
MISSING 1 → 'oci://<bucket>@<ns>/path' — confirm bucket-mapping config
VERDICT: 2 issues. Safe to proceed? (y / N / fix-first)
When to STOP and remediate first
If MISSING tables > 0, do NOT proceed to /migrate-job without resolving. Options surfaced to the user:
- "These schemas missing — run /migrate-catalog first?"
- "These S3 buckets unmapped — open aidp-bucket-mapping skill?"
- "These specific tables out of scope — exclude in manifest?"
- "Proceed anyway, accept Pass-2 failures at these reads?"
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 · 45 lines · 37 tokens per session scan A 5d6e29cdb14c
check-data is a command published in the GitHub repository ahmedawan-oracle/claude-code-plugins (4 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 518 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.
check-data compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| check-dataahmedawan-oracle/claude-code-plugins | Command | 4 | 3mo ago | MIT | A | 37 | Claude Code |
| initfcakyon/claude-codex-settings | Command | 1.2k | today | Apache-2.0 | A | 0 | Claude Code |
| securityajitpratap0/GoSQLX | Command | 124 | yesterday | Apache-2.0 | A | 21 | Claude Code |
| database-setupimsaif/design-with-claude | Command | 11 | 4d ago | MIT | A | 36 | Claude Code |
| new-migrationRaNDoM6913/claude-code-superkit | Command | 3 | yesterday | 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 |