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 schemachangegit 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/schemachange)<a href="https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/schemachange"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/schemachange/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/schemachange"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/schemachange.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.00639 |
| Opus 5.5 | $0.00021 | $0.00256 |
| Sonnet 5.5 | $0.00011 | $0.00128 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
schemachange 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 1mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schemachange
Deploy and manage Snowflake database changes using version control and CI/CD pipelines with schemachange's migration-based approach.
Quick Start
Script Types:
- V__ (Versioned) - One-time structural changes (run exactly once)
- R__ (Repeatable) - Objects that can be safely recreated (runs when new/modified)
- A__ (Always) - Scripts that run every deployment (must be idempotent)
Script Naming
Versioned Scripts (V__)
V1.0.0__initial_setup.sql
V1.1.0__create_base_tables.sql
V2.0.0__restructure_schema.sql
Use for: CREATE TABLE, ALTER TABLE, CREATE SCHEMA
Repeatable Scripts (R__)
R__Stage_01_create_views.sql
R__Stage_02_alter_procedures.sql
R__Stage_03_utility_functions.sql
Use for: CREATE OR ALTER VIEW, CREATE OR ALTER PROCEDURE, CREATE OR REPLACE STREAM
Always Scripts (A__)
A__refresh_permissions.sql
A__update_config_values.sql
Use for: Jobs that must run every deployment (idempotent only)
Key Concepts
Execution Order
- Versioned scripts (V__) in numeric order
- Repeatable scripts (R__) in alphabetic order (use naming to control)
- Always scripts (A__) in alphabetic order
CREATE OR ALTER vs CREATE OR REPLACE
- CREATE OR ALTER - Preserves data, tags, policies, grants (preferred)
- CREATE OR REPLACE - Drops and recreates (loses metadata)
See CREATE_OR_ALTER_REFERENCE.md for supported objects.
Configuration
# schemachange-config.yml
root-folder: migrations
create-change-history-table: true
connection-name: default
change-history-table: MY_DB.SCHEMACHANGE.CHANGE_HISTORY
Deployment
# Dry run
schemachange deploy --config-folder . --dry-run
# Deploy
schemachange deploy --config-folder .
# With variables
schemachange deploy --vars '{"env":"prod","schema":"data"}'
Resources
schemachange-config.yml- Complete configuration templateSCRIPT_PATTERNS.md- Examples for V**, R**, A__ scripts (coming soon)CREATE_OR_ALTER_REFERENCE.md- Supported object types (coming soon)CI_CD_EXAMPLES.md- GitHub Actions and Azure DevOps patterns (coming soon)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 97 lines · 53 tokens per session scan A eccd231f144b
schemachange is a skill published in the GitHub repository sfc-gh-dflippo/snowflake-dbt-demo (33 stars, last pushed today), licensed Apache-2.0. It adds 53 tokens to every session and 639 once invoked, about $0.0002 per session on Opus 5.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-08-30.
Other skills, from other repositories
atlas-onboard
Guided onboarding of a repository onto Atlas, one verified stage at a time: plan the units and the workflow, define the schema as code, set up the migration workflow, add CI with the Atlas Registry, deploy to staging, and promote to production. Each stage ends on a check the agent runs itself, such as a dry run with…
release-db-config-sync
Compute the remote DB migration + Nacos config diff before a test release — apc release db-config-sync really spawns sync-test-migrations.ts --dry-run (never a stub) and diffs Nacos key dumps, stopping at the write boundary. green(0) no diff · staged(3) pending migrations/missing keys await approval · blocked(1) real…
neon
Use when you have picked Neon (serverless Postgres) and need to connect correctly from a serverless or edge runtime, wire database branching into dev, preview and CI, or stop being burned by scale-to-zero cold starts and pooler limits — including choosing HTTP versus WebSocket connections and pooled versus direct…
end-to-end-snowflake-pipeline
Build an end-to-end Snowflake pipeline — ticket → dbt models + orchestration DAG → PR → self-review → ticket comment. Use when: (1) User says "build a pipeline for X end-to-end", "create an end-to-end flow", "set up the pipeline per JIRA-123" (2) Scope spans dbt models AND orchestration AND a PR — not just one of them…
513-frameworks-micronaut-db-migrations-flyway
Use when you need to add or review Flyway database migrations in a Micronaut application — micronaut-flyway, db/migration scripts, flyway.datasources. configuration, and alignment with JDBC or Micronaut Data. This should trigger for requests such as Add or review Flyway migrations in a Micronaut project; Configure…
database-testing
Validate database integrity, test migrations forward and backward, verify schema constraints, manage seed data, detect migration drift, and identify query performance issues. Covers PostgreSQL, MySQL, MongoDB with Prisma, TypeORM, Drizzle, and SQLAlchemy, plus Testcontainers test databases. Use when: "database test,"…