agentmods.dev

check-data

A pre-migration scan that reads a manifest and checks whether required tables and file paths exist and contain data on an AIDP cluster.

In plain words
What is it for?
It is for checking Spark read and table-write targets, reporting tables and paths as OK, MISSING, or EMPTY, and suggesting remediation.
Why use it?
It helps find missing or empty inputs before a migration job runs, reducing avoidable migration failures.

Command

2 29d ago A scan 37 tokens original MIT
View the source file ahmedawan-oracle/claude-code-plugins
Install

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.

agentmods
npx agentmods add commands/ahmedawan-oracle/claude-code-plugins/check-data
Clone the repo
git clone --depth 1 https://github.com/ahmedawan-oracle/claude-code-plugins
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 518 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.00518
Opus 5 $0.00018 $0.00259
Sonnet 5 $0.00007 $0.00104
Haiku 4.5 $0.00004 $0.00052

Measured 2d ago against content hash 5d6e29cdb14c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

claude-code-plugins/oracle-ai-data-platform-workbench-databricks-migrator/commands/check-data.md · 45 lines

What it actually says

/check-data — pre-migration scan

Light wrapper over aidp-check-data. Use before any aidp-migrate-job run.

Workflow

  1. Find an existing manifest at reports/<job>_manifest.json. If none, ask the user to build one via /migrate-job Phase 1, OR run aidp-build-dag.
  2. Invoke ${CLAUDE_PLUGIN_ROOT}/engine/scripts/check_data_availability.py (or _for_workflow.py if the manifest came from a Databricks Job ID).
  3. 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?"
Changes

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.

  1. 2d ago First seen · 45 lines · 37 tokens per session scan A 5d6e29cdb14c

Subscribe to this mod's changes

check-data is a command published in the GitHub repository ahmedawan-oracle/claude-code-plugins (2 stars, last pushed 29d ago), licensed MIT. It adds 37 tokens to every session and 518 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.

Related

Other commands, from other repositories

git

Git operations with intelligent commit messages and workflow optimization.

SuperClaude-Org/SuperClaude_Framework · 11 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

constitution

Create or update the project constitution from interactive or provided principle inputs.

github/spec-kit · 13 tokens