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 sfc-gh-dflippo/snowflake-dbt-demo --skill etl-validategit clone --depth 1 https://github.com/sfc-gh-dflippo/snowflake-dbt-demoWrote 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/etl-validate)<a href="https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/etl-validate"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/etl-validate/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/etl-validate"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/etl-validate.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.02305 |
| Opus 5 | $0.00030 | $0.01153 |
| Sonnet 5 | $0.00012 | $0.00461 |
| Haiku 4.5 | $0.00006 | $0.00231 |
Grade A, and why
etl-validate 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ETL Validate
Runs scai test etl-validate --platform <platform> against a single ETL code unit, verifying that the original source package and its Snowflake equivalent produce identical output. Requires the ETL unit to be deployed and a test YAML to exist for it.
Deploy, the test YAML, and connections are all enforced by the state machine, not this skill. etlValidate has deterministic preconditions: deploy (the unit is deployed to Snowflake), artifactExists on etl-test/*.y*ml (a kind: etl test YAML — .yml or .yaml, from etlSeed/scai test seed or hand-authored — is present under the unit's artifacts dir), and configureSourceConnectionExtract + configureSnowflakeTarget. The executor only dispatches this skill once all hold, so it is safe to run standalone (targeted directly at etlValidate): the machine will not dispatch it against an undeployed unit, one with no test YAML, or an unconfigured session. scai test etl-validate reads the connection details from the project's settings/test_config.yaml; named-connection overrides can be passed with -c / -s.
Step 0: Resolve Unit
Read the registry entry (the executor passes object_id; if entered by name, locate via migration_status(mode="my_objects_summary")):
| Field | Used as |
|---|---|
id |
{ETL_ID} for the --where filter |
source.platform |
{PLATFORM_ID} for --platform (ssis, informatica, …) — pass the registry's value verbatim, including its casing (sqlServer, not sqlserver) |
Step 0b: Platforms Without a Built-in Executor
Only ssis (SQL Agent / SSISDB) and informatica (pmcmd / dbt Cloud) have a built-in
executor. Any other kind: etl platform — DataStage, Talend, an in-house shell or binary
orchestrator — is rejected by --platform and by the seeder unless the project declares an
external_command: section in .scai/settings/test_config.yaml:
external_command:
side: source # source | target — required
command: ["/opt/etl/run.sh", "--full"] # required, argv list (no shell)
working_dir: /opt/etl # optional
env: {ETL_ENV: prod} # optional
wait_seconds: 300 # seed-time default for the emitted YAML
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 · 140 lines · 59 tokens per session scan A 73ec5a7c6933
etl-validate 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 59 tokens to every session and 2,305 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-10.
Other skills, from other repositories
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
shaft-automated-test-authoring
Use when implementing or repairing executable SHAFT Java tests for web, mobile, API, database, CLI, TestNG, JUnit, or Cucumber behavior.
shaft-database-testing
Use when implementing or repairing SHAFT.DB checks for persisted state, queries, rows, transactions, cleanup, or database-backed integration behavior.
multi-agent-e2e-validation
Multi-agent parallel E2E validation for database refactors. TRIGGERS - E2E validation, schema migration testing, database refactor validation.
schema-e2e-validation
Earthly E2E validation for YAML schema contracts. TRIGGERS - schema validation, YAML schema, schema contracts, regenerate types.
mock-and-fixture-generator
Generates realistic, edge-case-rich mock fixtures and synthetic API payloads without leaking real PII.