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-datasphere-plugin-for-claude-cowork --skill datasphere-cli-automatorgit clone --depth 1 https://github.com/MarioDeFelipe/sap-datasphere-plugin-for-claude-coworkWrote 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-datasphere-plugin-for-claude-cowork/datasphere-cli-automator)<a href="https://agentmods.dev/skills/mariodefelipe/sap-datasphere-plugin-for-claude-cowork/datasphere-cli-automator"><img src="https://agentmods.dev/badge/skills/mariodefelipe/sap-datasphere-plugin-for-claude-cowork/datasphere-cli-automator/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-datasphere-plugin-for-claude-cowork/datasphere-cli-automator"><img src="https://agentmods.dev/badge/skills/mariodefelipe/sap-datasphere-plugin-for-claude-cowork/datasphere-cli-automator.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.00074 | $0.04934 |
| Opus 5 | $0.00037 | $0.02467 |
| Sonnet 5 | $0.00015 | $0.00987 |
| Haiku 4.5 | $0.00007 | $0.00493 |
Grade C, and why
SAP Datasphere CLI Automator scanned grade C with 2 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 11d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -sL https://datasphere-cli.company.com/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL https://datasphere-cli.company.com/install.sh | bash How it starts
The opening of the file, as written. The whole thing — 781 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Datasphere CLI Automator
Overview
The SAP Datasphere CLI (Command-Line Interface) is the power user's gateway to programmatic administration and automation. While the Datasphere UI excels at interactive tasks, the CLI is your tool of choice when you need to:
- Bulk Operations: Provision hundreds or thousands of users, create multiple spaces, configure connections across landscapes
- Infrastructure-as-Code: Version control your Datasphere configuration in Git, deploy changes through pipelines
- Scheduled Automation: Trigger administrative tasks on schedules via cron, Task Chains, or cloud schedulers
- CI/CD Integration: Embed Datasphere provisioning into your DevOps pipeline (GitHub Actions, Azure DevOps, Jenkins)
- Headless Environments: Automate when no UI access is available or when running in containerized systems
CLI vs GUI: When to Use Each
| Scenario | CLI | GUI |
|---|---|---|
| Creating 500 users with attributes | ✓ | ✗ |
| Exploring data model visually | ✗ | ✓ |
| One-time user creation | Possible | ✓ |
| Batch certificate rotation | ✓ | ✗ |
| Setting up connection for testing | ✗ | ✓ |
| Deploying 10 connections across 5 systems | ✓ | ✗ |
| Configuring space capacity | ✓ | ✓ |
| Validating connection credentials | ✓ | ✓ |
Authentication and Setup
Before using the CLI, configure authentication to your Datasphere instance.
Service Key Authentication (Recommended for Automation)
Service keys are non-human identities ideal for automation, CI/CD, and scheduled tasks.
-
Create a Service Key in Datasphere:
- Navigate to System > Administration > Security
- Create a new service key with appropriate scope
- Download the key file (JSON format containing client ID, secret, URL)
-
Configure CLI with Service Key:
datasphere config init \ --client-id "your-client-id" \ --client-secret "your-client-secret" \ --instance-url "https://your-datasphere-instance.com" \ --auth-method service-key
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.
- 11d ago First seen · 781 lines · 74 tokens per session scan C fce14fedf0d5
SAP Datasphere CLI Automator is a skill published in the GitHub repository MarioDeFelipe/sap-datasphere-plugin-for-claude-cowork (25 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 4,934 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…