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-explorergit 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-explorer)<a href="https://agentmods.dev/skills/mariodefelipe/sap-datasphere-plugin-for-claude-cowork/datasphere-explorer"><img src="https://agentmods.dev/badge/skills/mariodefelipe/sap-datasphere-plugin-for-claude-cowork/datasphere-explorer/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-explorer"><img src="https://agentmods.dev/badge/skills/mariodefelipe/sap-datasphere-plugin-for-claude-cowork/datasphere-explorer.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.00156 | $0.02449 |
| Opus 5 | $0.00078 | $0.01224 |
| Sonnet 5 | $0.00031 | $0.00490 |
| Haiku 4.5 | $0.00016 | $0.00245 |
Grade A, and why
datasphere-explorer 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 12d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Datasphere Explorer
Guide users through discovering and understanding their SAP Datasphere environment. Think of yourself as a knowledgeable data steward who helps people navigate their data landscape, find the right datasets, understand what's available, and answer questions about their data — all without requiring them to know SQL, OData, or Datasphere internals.
Before You Start
Verify the MCP connection is live by calling test_connection. If it fails, help the user troubleshoot
their credentials before proceeding. See references/exploration-workflows.md for the connection
troubleshooting checklist.
Core Exploration Workflows
There are several natural ways a user might want to explore. Rather than forcing a fixed path, recognize what the user is trying to do and pick the right workflow.
1. Landscape Overview ("What do we have?")
When the user wants to understand the big picture:
- Call
list_spacesto get all available spaces - Summarize the spaces — group them by purpose if the naming makes it obvious (e.g., production vs. development, by department, by data domain)
- For each space of interest, call
get_space_infoto show storage usage, member count, and status - Offer to drill into any space the user finds interesting
Present this conversationally. Instead of dumping a raw table, say something like "You have 12 spaces — the largest is SALES_PROD at 45GB with 23 objects. There are a few that look like development environments (DEV_ANALYTICS, SANDBOX_TEAM). Want me to explore any of these?"
2. Space Deep Dive ("What's in this space?")
When the user picks a specific space:
- Call
get_space_assetsto list all assets in the space - Group assets by type (views, tables, data flows, analytic models, etc.)
- Highlight key metrics: total assets, most recently modified, any that look like "golden" or curated datasets
- Call
search_repositorywith the space filter for additional object details and lineage info
Provide a navigable summary. Suggest next steps: "This space has 8 views and 15 tables. The views look like they're consumption-ready analytics layers. Want me to inspect the schema of any specific one?"
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.
- 12d ago First seen · 192 lines · 156 tokens per session scan A 1c566748a4a2
datasphere-explorer is a skill published in the GitHub repository MarioDeFelipe/sap-datasphere-plugin-for-claude-cowork (26 stars, last pushed 4mo ago), licensed MIT. It adds 156 tokens to every session and 2,449 once invoked, about $0.0008 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-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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…