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 build-mosaic-modelgit 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/build-mosaic-model)<a href="https://agentmods.dev/skills/mstr-sharma/strategy-automate/build-mosaic-model"><img src="https://agentmods.dev/badge/skills/mstr-sharma/strategy-automate/build-mosaic-model/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/build-mosaic-model"><img src="https://agentmods.dev/badge/skills/mstr-sharma/strategy-automate/build-mosaic-model.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.00000 | $0.03040 |
| Opus 5 | $0.00000 | $0.01520 |
| Sonnet 5 | $0.00000 | $0.00608 |
| Haiku 4.5 | $0.00000 | $0.00304 |
Grade A, and why
build-mosaic-model 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build a Strategy Mosaic model from scratch
This skill is the execution layer for Mosaic data-model creation and modification. The planning layer is skills/strategy-data-modeling/SKILL.md — route through it first unless the user gave you a complete pre-planned build.
Out of scope for this skill — route to skills/strategy-automation/SKILL.md and memory/reference_strategy_surface_matrix.md:
- Classic / project semantic-layer objects (legacy attributes, project metrics/facts/filters, project security filters)
- Runtime analytics (reports, dashboards, documents, prompt answers, exports)
- AI / Agent / Bot work
- Non-Mosaic cube / dataset work (Intelligent Cube, OLAP cube, Super Cube, MTDI, Push Data)
- Subscriptions, users, groups, roles, VLDB, object administration
Load these memory files on entry
Every one of these owns a piece of the build surface; this skill delegates the detail to them. Load before synthesizing any payload.
memory/reference_strategy_error_codes.md— grep this FIRST on any 4xx/5xx before looking anywhere else.memory/reference_data_modeling_foundations.md— Kimball: grain, conformed dims, star/snowflake/galaxy/bridge topology, additivity classes.memory/reference_mosaic_business_logic_translation.md— intent → build plan; the mandatory pre-build artifact.memory/feedback_business_logic_pass_mandatory.md— non-optional rule.memory/feedback_mosaic_relationship_wiring.md— conformed-dim recipe + the8004ccdb/8004ccc7/8004e409failure modes + fix pattern.memory/feedback_build_mosaic_session_leak.md— one-session-one-process rule; the single most common cause of mid-build failure.memory/reference_mosaic_rest_api.md— verified endpoint paths (auth, datasources, catalog, data models, changesets, security, translations).memory/reference_mosaic_modeling_concepts.md— payload shapes for attributes, metrics (compound / conditional / level / transformation), relationships, filters, transformations.memory/reference_mosaic_publish_path.md— the one publish file: 3-step flow, do-not-fire-both rule, dataType publish-readiness gate (prevents iServerCode -2147212544 stalls).memory/reference_mosaic_vs_legacy_surfaces.md— subType 779 vs 776 classification before any publish/refresh/execute write.memory/reference_strategy_object_cloning.md— clone-and-remap procedure when a payload shape is unknown.memory/feedback_mosaic_ship_bar.md— ship-bar checklist: naming, DESC-form report/browse displays, metric format tokens, description length cap, SF naming.
What ships with it
14 files 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.
- examples/attribute_plan_template.yaml 417 B
- examples/model_plan_template.yaml 1.5 KB
- examples/relationship_plan_template.yaml 345 B
- examples/validation_suite_template.yaml 540 B
- scripts/_client.py 17 KB runs code
- scripts/build_mosaic.py 225 KB runs code
- scripts/mosaic_safety.py 14 KB runs code
- scripts/preflight_model_check.py 17 KB runs code
- scripts/schema_object_translator.py 20 KB runs code
- scripts/strategy_mosaic_inventory.py 18 KB runs code
- scripts/strategy_semantic_inventory.py 18 KB runs code
- scripts/strategy_semantic_mine.py 21 KB runs code
- scripts/strategy_validate_models.py 17 KB runs code
- scripts/strategy_validate.py 32 KB runs code
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 · 176 lines · 0 tokens per session scan A 212dcc795f02
build-mosaic-model is a skill published in the GitHub repository mstr-sharma/strategy-automate (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,040 tokens. 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…
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…