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.
npx agentmods add commands/mariodefelipe/sap-bdc-plugin/bdc-diagnosegit clone --depth 1 https://github.com/MarioDeFelipe/sap-bdc-pluginWrote 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/mariodefelipe/sap-bdc-plugin/bdc-diagnose)<a href="https://agentmods.dev/commands/mariodefelipe/sap-bdc-plugin/bdc-diagnose"><img src="https://agentmods.dev/badge/commands/mariodefelipe/sap-bdc-plugin/bdc-diagnose.svg" alt="Measured on agentmods" 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.00017 | $0.00305 |
| Opus 5 | $0.00009 | $0.00152 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
bdc-diagnose 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 6d 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
You are running the /bdc-diagnose command.
The user is pasting an error message in $ARGUMENTS. If it is empty, ask them to paste the full error text (including error code, request ID, and timestamp if available) and stop.
Steps:
-
Call
diagnose_share_errorfrom thesap-bdcMCP server witherror_message=$ARGUMENTS. -
If the tool returns a matching SAP Note, present it in this shape:
### Matches SAP Note <NUMBER>: <title> **Cause:** <1–2 sentences> **Resolution:** 1. … 2. … **Related tool you can run right now:** <tool name and suggested args, if applicable> -
If no note matches, activate the
bdc-troubleshooterskill for a broader search across the 18 indexed notes. If still no match, advise the user to:- Check SAP Note 3653192 (main Databricks/BDC troubleshooting guide)
- Prepare a support case per SAP Note 3568017, including request ID, tenant ID, and timestamp
Never invent SAP Note numbers or make up resolution steps. If the diagnosis is uncertain, say so and explain what further information would disambiguate.
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.
- 6d ago First seen · 34 lines · 17 tokens per session scan A 5273a9773e39
bdc-diagnose is a command published in the GitHub repository MarioDeFelipe/sap-bdc-plugin (9 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 305 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.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.