Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sfc-gh-dflippo/snowflake-dbt-demonpx agentmods add skills/sfc-gh-dflippo/snowflake-dbt-demo/data-strategyWrote 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/sfc-gh-dflippo/snowflake-dbt-demo/data-strategy)<a href="https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/data-strategy"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/data-strategy/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/sfc-gh-dflippo/snowflake-dbt-demo/data-strategy"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/data-strategy.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.00049 | $0.00722 |
| Opus 5 | $0.00024 | $0.00361 |
| Sonnet 5 | $0.00010 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
data-strategy 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 2d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capture Data Strategy
Capture the project's data migration and validation strategy by driving the existing
data-migration-setup and data-validation-setup wizards to completion. This skill only drives
those two wizards — it asks no new questions of its own (the questions live in those machines) and makes
no assumptions about who invoked it. Deciding whether to capture the strategy is the caller's job; when
this skill runs, it runs the wizards.
For a Snowflake-source validation-only project, skip Step 1 and run only the validation wizard in Step 2. Snowflake is already the source and target, so data migration is not available.
Step 1 — Migration strategy (non-Snowflake sources only)
Drive the data-migration-setup machine to completion: call progress_setup(mode="data_migration") in a
loop until the response's completed is true — ask each response's next_prompt (plus any then_ask,
in the same turn) and send the answers back with progress_setup(mode="data_migration", answers={...}).
If the strategy was already chosen (e.g. a prior migration set it lazily), the first call returns
completed: true immediately — do not re-prompt.
Step 2 — Validation strategy
Then drive the data-validation-setup machine the same way: progress_setup(mode="data_validation") in
a loop until completed. An already-chosen strategy returns completed: true at once.
The choices persist to plugin.yml as data_migration_type, data_migration_sync_strategy,
data_migration_extraction_strategy, data_migration_target_table_type (Redshift), data_validation_type,
and data_validation_sync_strategy.
Changing an existing choice
Only the main/setup agent changes persisted strategy. A per-object
migrateData / validateData subagent must return the request to its parent
instead of re-running setup or changing infrastructure.
When the user explicitly asks for a different strategy, confirm the new choice
once and apply it through the corresponding setup tool. For example, changing
an existing full load to incremental watermark means calling
migrate_data(mode="setup", migration_type="incremental", sync_strategy="watermark", force_regenerate=true, where=...), then reviewing
the regenerated workflow and setting its real watermarkColumn (plus
primaryKeyColumns / trackModifications when required for an already
populated target). Explicit setup arguments persist the new defaults in
plugin.yml; subsequent object dispatches reuse them without asking again.
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.
- 2d ago First seen · 62 lines · 49 tokens per session scan A d4ebf3e2fb3b
data-strategy is a skill published in the GitHub repository sfc-gh-dflippo/snowflake-dbt-demo (33 stars, last pushed 3d ago), licensed Apache-2.0. It adds 49 tokens to every session and 722 once invoked, about $0.0002 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-09-10.
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…