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 mstr-sharma/strategy-automate --skill strategy-data-modelinggit clone --depth 1 https://github.com/mstr-sharma/strategy-automateWrote 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/mstr-sharma/strategy-automate/strategy-data-modeling)<a href="https://agentmods.dev/skills/mstr-sharma/strategy-automate/strategy-data-modeling"><img src="https://agentmods.dev/badge/skills/mstr-sharma/strategy-automate/strategy-data-modeling/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/mstr-sharma/strategy-automate/strategy-data-modeling"><img src="https://agentmods.dev/badge/skills/mstr-sharma/strategy-automate/strategy-data-modeling.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.00079 | $0.01212 |
| Opus 5 | $0.00039 | $0.00606 |
| Sonnet 5 | $0.00016 | $0.00242 |
| Haiku 4.5 | $0.00008 | $0.00121 |
Grade A, and why
strategy-data-modeling 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 9d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategy Data Modeling (Kimball-first planning layer)
Use this skill when the user asks to design, inspect, explain, review, migrate, validate, or improve a Strategy / MicroStrategy semantic model. This skill is the planning layer that sits between strategy-automation (which classifies the surface) and execution skills (skills/build-mosaic-model/SKILL.md, skills/strategy-validation/SKILL.md).
Skill precedence (one-way, no loops):
strategy-automation (classify surface)
└─► strategy-data-modeling (plan — this skill)
└─► skills/build-mosaic-model/SKILL.md (build-mosaic-model) OR legacy mining
└─► strategy-validation (verify)
Do NOT route back up the chain. This skill calls execution skills; execution skills do not call this one.
Required memory (load on entry)
Kimball foundations (load first, every time):
memory/reference_data_modeling_foundations.md— the ONE Kimball design file: grain, conformed dims, star/snowflake topology, additivity, anti-patterns, plus sections for Strategy schema objects (Kimball → object mapping), Attribute design, Fact and metric design, Relationship design, Hierarchy design, and Time modelingmemory/reference_strategy_data_validation.md— 10-check design suite + 5-query runnable suite
Mosaic work (additional):
memory/checklist_strategy_automation_modeling_playbook.md— mandatory pre-build pass: surface routing, build sequence, changeset/rollback gates, publish readiness, validation close-outmemory/feedback_mosaic_relationship_wiring.md— conformed-dim encoding + error-code fix recipesmemory/feedback_mosaic_ship_bar.md
Classic / migration (additional):
memory/reference_strategy_legacy_to_mosaic_mining.md— start-here hub; classic inventory checklist + object→Mosaic migration mapping
Output contract — Kimball-first model plan
For any modeling request, produce or update a model plan containing:
- Topology declaration —
star | snowflake | galaxy | bridge-heavy | non-Kimball. Non-Kimball stops the work and confirms with the user. - Table classification — every input table labeled
fact | dim | bridge | snowflake_parent_dim | degenerate_dim | noise. - Business process
- Declared grain (per fact table)
- Conformed-dim enumeration — every entity that appears in ≥2 tables, with the list of (table, column) expressions it must span
- Source systems and tables
- Attributes and forms
- Facts
- Governed metrics (each tagged with additivity class:
additive | semi-additive | non-additive | derived) - Relationships (parent/child/relationship_table/type, and the archetype from
reference_mosaic_relationship_archetypes.md) - Hierarchies
- Time roles and transformations
- Security / governance notes
- Assumptions and open questions
- Validation suite
- Build sequence
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.
- 9d ago First seen · 126 lines · 79 tokens per session scan A 08fd55b261d4
strategy-data-modeling is a skill published in the GitHub repository mstr-sharma/strategy-automate (2 stars, last pushed 4d ago), licensed MIT. It adds 79 tokens to every session and 1,212 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-31.
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…