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-analytic-model-creatorgit 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-analytic-model-creator)<a href="https://agentmods.dev/skills/mariodefelipe/sap-datasphere-plugin-for-claude-cowork/datasphere-analytic-model-creator"><img src="https://agentmods.dev/badge/skills/mariodefelipe/sap-datasphere-plugin-for-claude-cowork/datasphere-analytic-model-creator/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-analytic-model-creator"><img src="https://agentmods.dev/badge/skills/mariodefelipe/sap-datasphere-plugin-for-claude-cowork/datasphere-analytic-model-creator.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.00071 | $0.04376 |
| Opus 5 | $0.00036 | $0.02188 |
| Sonnet 5 | $0.00014 | $0.00875 |
| Haiku 4.5 | $0.00007 | $0.00438 |
Grade A, and why
Analytic Model Creator 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 — 706 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytic Model Creator Skill
Overview
The Analytic Model Creator skill guides you through designing and implementing Analytic Models in SAP Datasphere. Analytic Models are semantic objects that present data to analytics tools like SAP Analytics Cloud (SAC) in a consumable, pre-aggregated format. They sit above Fact and Dimension views, providing a polished interface for end users to create reports and dashboards.
What Are Analytic Models?
Definition
An Analytic Model is a semantic object that combines:
- One Fact source — Contains quantitative measures and primary grain
- Multiple Dimensions — Provide context and analysis dimensions
- Measures — Simple, calculated, or restricted aggregations
- Variables — Optional parameters for dynamic filtering
- Attributes — Dimension properties and drill-down paths
- Aggregations — Exception rules for special measure handling
Role in the Consumption Layer
Raw Data (Databases)
↓
Data Builder (Cleanse, Join)
↓
Semantic Views (Graphical/SQL)
↓
Analytic Models (Aggregated, Structured) ← YOU ARE HERE
↓
SAC Dashboards, Reports, Exploration
When to Use Analytic Models
Create an Analytic Model when:
- Building SAC dashboards and reports
- End users need self-service analytics
- You need to define sophisticated aggregation rules
- Measures require conditional aggregation or currency conversion
- Multiple consumption patterns are needed from one data source
- Data governance requires controlled access to metrics
DO NOT use Analytic Models for:
- Pure data integration or distribution
- Direct operational reporting (use Relational Datasets)
- Real-time transaction querying (use transaction views)
- Data that rarely needs aggregation
Creating an Analytic Model: Step-by-Step
Step 1: Select a Fact Source
Choose the fact table that contains your measurable events or transactions.
Fact source selection criteria:
- Must be a view with semantic usage = "Fact"
- Contains quantitative measures (amounts, counts, quantities)
- Has appropriate grain for analysis (transaction, daily, order level)
- Includes necessary dimensional keys
- Consider data volume and refresh frequency
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 · 706 lines · 71 tokens per session scan A 6651135211db
Analytic Model Creator 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 71 tokens to every session and 4,376 once invoked, about $0.0004 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…
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…