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 skills add MarioDeFelipe/sap-bdc-plugin --skill bdc-intelligent-appsgit 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/skills/mariodefelipe/sap-bdc-plugin/bdc-intelligent-apps)<a href="https://agentmods.dev/skills/mariodefelipe/sap-bdc-plugin/bdc-intelligent-apps"><img src="https://agentmods.dev/badge/skills/mariodefelipe/sap-bdc-plugin/bdc-intelligent-apps/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/mariodefelipe/sap-bdc-plugin/bdc-intelligent-apps"><img src="https://agentmods.dev/badge/skills/mariodefelipe/sap-bdc-plugin/bdc-intelligent-apps.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.00093 | $0.01759 |
| Opus 5 | $0.00046 | $0.00879 |
| Sonnet 5 | $0.00019 | $0.00352 |
| Haiku 4.5 | $0.00009 | $0.00176 |
Grade A, and why
bdc-intelligent-apps 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP BDC Intelligent Applications
Intelligent Applications Lifecycle
Installing Intelligent Applications
An SAP BDC administrator installs intelligent applications into SAP Datasphere and SAP Analytics Cloud tenants. Installation automatically creates three SAP-managed spaces:
- Ingestion space: Contains data products as local tables and replication flows that load data from source systems.
- Preparation space: Contains views built on data products for consumption preparation.
- App space: Contains analytic models exposed to SAP Analytics Cloud (named after the intelligent application).
These spaces are read-only and SAP-managed—objects cannot be created, shared, or imported/exported manually. Data flows from source system → SAP Datasphere → combined/prepared for analytics → exposed in SAP Analytics Cloud as stories.
Multiple Installations & Shared Ingestion Spaces
Multiple instances of a single intelligent application can be installed for different source systems:
- Each instance gets its own set of three spaces, distinguished by a system alias assigned during installation.
- Multiple intelligent applications can be installed for the same source system, reusing the shared ingestion space.
- When uninstalling, only relevant spaces are removed; the shared ingestion space is retained until the final application is removed.
Reviewing Installed Intelligent Applications
Users with appropriate space access can:
- View objects in standard editors (read-only).
- Monitor data flow from source to SAC stories.
- If task chains exist, DW Integrator-role users must run each chain at least once and create a schedule for regular runs.
Row-Level Security for Intelligent Application Data
By default, no user can view data in delivered SAP Analytics Cloud stories. Row-level security uses data access controls:
- Identify fact views and permissions table in the preparation space.
- Prepare permissions records in operator/values format for row-level access:
- Use
ALLor*operator to show all records to selected user. - Avoid more than 5,000 permissions records per user for performance.
- Use
- Upload permissions data as CSV file (see Load or Delete Local Table Data).
- Optionally review accessible data using View as User dialog.
- Maintain permissions table as necessary.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 155 lines · 93 tokens per session scan A 99d3ef6ef85c
bdc-intelligent-apps is a skill published in the GitHub repository MarioDeFelipe/sap-bdc-plugin (9 stars, last pushed 4mo ago), licensed MIT. It adds 93 tokens to every session and 1,759 once invoked, about $0.0005 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.