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/register-sas-source-unitsWrote 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/register-sas-source-units)<a href="https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/register-sas-source-units"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/register-sas-source-units/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/register-sas-source-units"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/register-sas-source-units.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.00100 | $0.00949 |
| Opus 5 | $0.00050 | $0.00475 |
| Sonnet 5 | $0.00020 | $0.00190 |
| Haiku 4.5 | $0.00010 | $0.00095 |
Grade A, and why
register-sas-source-units 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Register SAS Source Units into the Code Unit Registry
© Snowflake Inc. This skill and its contents are the proprietary intellectual property of Snowflake Inc.
Purpose: Bridge the isolated SAS conversion track to the existing scai test
regression harness by writing Code Unit Registry (CUR) entries directly as JSON
from the SAS source files. This is the first of two registration steps; the second
(register-sas-converted-units) attaches the converted .sql.
Boundary (do not cross): This writes registry/<id>.json files only. It does
not register a SnowConvert source dialect, touch the .NET CodeUnitRegistry
engine, add SAS to MCP state machines, or join AIM claims/waves. See
../INTEGRATION.md. The contract for the JSON it writes is ../references/cur-schema.md.
When to use
- After (or alongside) a SAS conversion, when the user wants to run
scai test(seed/validate) against the converted output. - Automatically invoked by
convert-sas-to-snowflakepost-conversion (see that skill's wiring), or run standalone against an existing.sascorpus.
Inputs
- SAS source — a
.sasfile or a directory of them. - Project root — the SAS conversion
<output_dir>. Gains a.scai/marker plus siblingregistry/,source/,snowflake/,artifacts/dirs soscai testrecognizes it as a project. - Target schema (optional) —
DB.SCHEMAthe converted objects will live in.
Workflow
-
Resolve the project root. Default to the conversion
<output_dir>. If an existing.scai/project is present elsewhere, confirm with the user before scaffolding a new one (do not collide with an AIM project). -
Run the emitter (deterministic, stdlib-only Python — no Snowflake needed):
cd ../assess-sas-migration/tool python3 emit_cur.py source \ --sas <dir_or_file> \ --project-root <output_dir> \ --source-root <dir> \ --target-schema DB.SCHEMAFor each SAS file it writes one source-side unit:
source.platform = "sas",objectTypeinferred from the parsed blocks (macro/DATA-step logic ->procedure; pure table-building ->table), file-level dependency edges from the cross-file graph, and asignaturefrom any%MACROparameters. The.sasfile is copied undersource/and md5-checksummed. -
Report the counts by objectType and note that only
procedure/function/macrounits will producescai testcases (tables register but are not proc-tested). Tier-3 (PySpark) files are not SQL objects and are left for the converted pass to skip. -
Next step: run
register-sas-converted-unitsonce conversion output exists to attachfiles.convertedand confirm objectType from the generated SQL.
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 · 74 lines · 100 tokens per session scan A 2b9aeb99407f
register-sas-source-units 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 100 tokens to every session and 949 once invoked, about $0.0005 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.