bdc-validate-share

bdc-validate-share is a command for coding agents from MarioDeFelipe/sap-bdc-plugin. It costs 18 tokens per session (322 once invoked), scanned A, original, MIT.

A command that checks whether a Databricks data share is ready to be registered with SAP Business Data Cloud. A data share is a collection of tables made available to another system or organisation.

In plain words
What is it for?
Use it before registering a share to review its tables and ownership, check BDC registration readiness, detect deletion vectors, and get a ready-or-not-ready verdict.
Why use it?
It gathers the main pre-flight checks in one place, including whether the share exists, has the right grants, and contains deletion vectors that could block publishing.

Command

Part of the sap-bdc plugin — 7 skills, 4 commands, 1 MCP server shipped together

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/mariodefelipe/sap-bdc-plugin/bdc-validate-share
Clone the repo
git clone --depth 1 https://github.com/MarioDeFelipe/sap-bdc-plugin

Or install sap-bdc, the plugin that ships this one along with the rest of its 7 skills, 4 commands, 1 MCP server.

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

agentmods badge for bdc-validate-share

README.md
[![agentmods](https://agentmods.dev/badge/commands/mariodefelipe/sap-bdc-plugin/bdc-validate-share.svg)](https://agentmods.dev/commands/mariodefelipe/sap-bdc-plugin/bdc-validate-share)
Your own site
<a href="https://agentmods.dev/commands/mariodefelipe/sap-bdc-plugin/bdc-validate-share"><img src="https://agentmods.dev/badge/commands/mariodefelipe/sap-bdc-plugin/bdc-validate-share.svg" alt="Measured on agentmods" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 322 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.00018 $0.00322
Opus 5 $0.00009 $0.00161
Sonnet 5 $0.00004 $0.00064
Haiku 4.5 $0.00002 $0.00032

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

Security

Grade A, and why

bdc-validate-share 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 5d 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.

commands/bdc-validate-share.md · 40 lines

What it actually says

You are running the /bdc-validate-share command.

The user wants to validate the share whose name appears in $ARGUMENTS. If $ARGUMENTS is empty, ask the user for the share name and stop.

Run these tools from the sap-bdc MCP server in order and collect all results:

  1. validate_share_readiness with share_name=$ARGUMENTS, check_bdc_registration=true — confirms the share exists, has tables, is granted to the recipient.

  2. get_share_details with share_name=$ARGUMENTS — shows table list, owner, creation info.

  3. check_deletion_vectors with share_name=$ARGUMENTS — pre-flight check for SAP Note 3706399 (Deletion Vectors break CSN publish).

Present a single consolidated verdict:

### Pre-flight validation for share: <name>

✅ / ❌ Existence & grants (validate_share_readiness)
✅ / ❌ Deletion Vectors (SAP Note 3706399)
ℹ️  Objects: <N> tables, latest added <timestamp>

### Verdict: READY / NOT READY

Blocking issues:
  - …

Recommended next step:
  <concrete tool call or SQL>

If any step fails unexpectedly, cite the error verbatim and suggest /bdc-diagnose with the error text as input.

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. 5d ago First seen · 40 lines · 18 tokens per session scan A 0f2b621cc82b

Subscribe to this mod's changes

bdc-validate-share is a command published in the GitHub repository MarioDeFelipe/sap-bdc-plugin (9 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 322 once invoked, about $0.0001 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.