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 seed-scriptgit 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/seed-script)<a href="https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/seed-script"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/seed-script/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/seed-script"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/seed-script.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.00044 | $0.01400 |
| Opus 5 | $0.00022 | $0.00700 |
| Sonnet 5 | $0.00009 | $0.00280 |
| Haiku 4.5 | $0.00004 | $0.00140 |
Grade A, and why
seed-script 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.
Seed BTEQ Script Inputs
Executor for the seedScript task. The CUR declares which shell variables each BTEQ script binds and their kind; the values live in the shell script that sets them before invoking bteq (export UTIL_DB=PROD_UTIL, CFG=${1}.cfg, RUN_DATE=`date +%Y%m%d`) — not in the .btq. scai test seed --bindings-from <shell-script> reads those scripts, pre-fills the binding values, and stages .IMPORT fixtures, so you hand-fill only what genuinely can't be resolved. Capture runs after this against the filled YAML, so leave no placeholder behind. YAML shapes: ../../references/BTEQ_TEST_YAML.md.
Seed the whole BTEQ set in one pass, not one unit at a time: a variable that recurs across scripts is hoisted to the global .scai/settings/test_config.yaml and filled once. Run this the first time any BTEQ unit reaches seedScript — it seeds every BTEQ unit together, so the rest are already done (idempotent; re-runs preserve filled values).
Per binding, the value resolves from the first tier that can supply it: shell-script literal → ${N} arg → capture-time { eval } → __REPLACE_ME__ (manual).
Step 1: Ask the user for the BTEQ shell script(s)
Ask for the shell script(s) that set the BTEQ variables and run bteq (e.g. runSqlScript_*.sh), given as file paths or a directory (scanned recursively for *.sh / *.ksh / *.bash; source / . includes are followed when locatable). If a shell script derives values from invocation arguments (CFG=${1}.cfg, . /etc/$1.cfg), also ask for those positional arguments, in order ($1 first).
Collect the path(s) and args only — don't open, read, or trace the shell script to work out which bindings resolve. The seed parses it and reports what it couldn't resolve (Step 3); pre-analyzing here just duplicates that work.
If the user has no shell script, seed without --bindings-from; every value drops to the manual tier (Step 3).
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 · 44 tokens per session scan A 77fc1cbc741e
seed-script 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 44 tokens to every session and 1,400 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
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
compiler-port
Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
platform-detection
Identify a .NET project's test platform, framework, command mode, and SDK-style vs classic project system. Use only for "which test platform/framework?", "VSTest or MTP?", or "what runner does this project use?", including bridge settings, UseVSTest opt-outs, and incompatible or conflicting VSTest/MTP configuration.…
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…