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/skills/ahmedawan-oracle/claude-code-plugins/aidp-build-dag)<a href="https://agentmods.dev/skills/ahmedawan-oracle/claude-code-plugins/aidp-build-dag"><img src="https://agentmods.dev/badge/skills/ahmedawan-oracle/claude-code-plugins/aidp-build-dag/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/skills/ahmedawan-oracle/claude-code-plugins/aidp-build-dag"><img src="https://agentmods.dev/badge/skills/ahmedawan-oracle/claude-code-plugins/aidp-build-dag.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.00089 | $0.01239 |
| Opus 5 | $0.00044 | $0.00620 |
| Sonnet 5 | $0.00018 | $0.00248 |
| Haiku 4.5 | $0.00009 | $0.00124 |
Grade A, and why
aidp-build-dag 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 8d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aidp-build-dag — build the migration manifest
The execution DAG is what the migrator reads to know which notebooks to migrate, in what order, with what dependencies. Build it once per workload.
When to use
- User asks "what would migrate", "show me the dependency tree", "build the manifest".
- Before any
aidp-migrate-jobinvocation against a new workload. - After changing the Databricks workspace path or workflow ID.
Two entry points
The migrator ships two DAG builders. Pick based on input shape:
| Input | Entrypoint |
|---|---|
Path-based: a folder of .ipynb / .py notebooks the user wants migrated |
${CLAUDE_PLUGIN_ROOT}/engine/scripts/build_dag.py |
| Workflow-based: a Databricks Job ID whose tasks the user wants migrated, preserving the task DAG | ${CLAUDE_PLUGIN_ROOT}/engine/scripts/build_dag_from_workflow.py |
Path-based invocation
python3 ${CLAUDE_PLUGIN_ROOT}/engine/scripts/build_dag.py \
--root "<databricks-workspace-path>" \
--job-name "<MyJob>" \
--output reports/<MyJob>_manifest.json
--root— Databricks workspace folder containing the entry notebooks. The script walks every*.ipynb/*.pyunder this prefix.--job-name— a name for the manifest (used as the output-base subdirectory).--output— manifest write path.
The builder follows %run chains AND dbutils.notebook.run(...) calls to build a topo-ordered DAG. It also flags transitive deps so Pass-1 knows which notebooks to migrate code-only first.
Workflow-based invocation
python3 ${CLAUDE_PLUGIN_ROOT}/engine/scripts/build_dag_from_workflow.py \
--job-id <databricks-job-id> \
--output reports/<MyJob>_manifest.json
This pulls the Job's task definitions via the Databricks Jobs REST API and converts depends_on task edges into the manifest's DAG. Use when the user wants the AIDP migration to mirror the Databricks Workflow shape (vs. just inferring dependencies from %run).
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.
- 8d ago First seen · 112 lines · 89 tokens per session scan A d04f9db19b57
aidp-build-dag is a skill published in the GitHub repository ahmedawan-oracle/claude-code-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 1,239 once invoked, about $0.0004 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
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.