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 vaquarkhan/data-engineering-agent-skills --skill snowflake-native-pipelines-and-governancegit clone --depth 1 https://github.com/vaquarkhan/data-engineering-agent-skillsWrote 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/vaquarkhan/data-engineering-agent-skills/snowflake-native-pipelines-and-governance)<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/snowflake-native-pipelines-and-governance"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/snowflake-native-pipelines-and-governance/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/vaquarkhan/data-engineering-agent-skills/snowflake-native-pipelines-and-governance"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/snowflake-native-pipelines-and-governance.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.00059 | $0.00665 |
| Opus 5 | $0.00030 | $0.00332 |
| Sonnet 5 | $0.00012 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
snowflake-native-pipelines-and-governance 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Snowflake Native Pipelines And Governance
Overview
Use this skill when Snowflake is not just the storage target but the primary pipeline and governance surface. It helps agents reason about native ingestion, incremental patterns, task orchestration, governance controls, warehouse sizing, and secure publish paths inside Snowflake.
When to Use
- building warehouse-native incremental pipelines in
Snowflake - designing with
Streams,Tasks, orDynamic Tables - evaluating
Snowpipe,Snowpark, or external orchestration boundaries - defining masking, row access, tags, and secure sharing in the same workflow
- reviewing publish readiness for Snowflake-native data products
Do not assume Snowflake-native is automatically the right answer for every compute and orchestration step.
Workflow
-
Define the execution boundary. Decide what should stay inside
Snowflakeversus what belongs in upstream landing, external orchestration, or other compute services. -
Choose the incremental pattern. Consider:
StreamsTasksDynamic TablesSnowpipe- external orchestration when boundaries are broader than Snowflake alone
-
Design governance and access together. Include:
- roles
- masking policies
- row access policies
- tags and classification
- secure publish or sharing boundaries
-
Make warehouse operations explicit. Cover:
- warehouse sizing
- concurrency and isolation
- cost controls
- retry and rerun behavior
- validation before publish
-
Define publish and recovery behavior. Require:
- reconciliation or validation gates
- controlled reopen after failure
- rollback or forward-fix plan for warehouse-native publishes
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "Because the data is in Snowflake, the pipeline should also live there." | Some landing, preprocessing, orchestration, or resilience controls still belong outside the warehouse. |
| "Tasks prove the pipeline is production-ready." | Task success alone does not prove contract correctness, reconciliation, or secure publish behavior. |
| "Masking can be added after the model is stable." | Governance controls are part of the design, not cleanup after delivery. |
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 · 80 lines · 59 tokens per session scan A 8fbc657c73f6
snowflake-native-pipelines-and-governance is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (45 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 665 once invoked, about $0.0003 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-03.
Other skills, from other repositories
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
sl
Skill "sl" from Kaelio/ktx, covering semantic layer, part 1 - schema reference, overlay sources, standalone table sources and standalone sql sources.
historic_sql_table_digest
Convert one changed historic-SQL table usage bucket into typed table usage evidence for deterministic schema projection.
live_database_ingest
Capture semantic-layer and knowledge updates from a live database schema snapshot.
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.