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 hicham-bab/dbt-legacy-migration-skills --skill migrating-stored-procedures-to-dbtgit clone --depth 1 https://github.com/hicham-bab/dbt-legacy-migration-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/hicham-bab/dbt-legacy-migration-skills/migrating-stored-procedures-to-dbt)<a href="https://agentmods.dev/skills/hicham-bab/dbt-legacy-migration-skills/migrating-stored-procedures-to-dbt"><img src="https://agentmods.dev/badge/skills/hicham-bab/dbt-legacy-migration-skills/migrating-stored-procedures-to-dbt/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/hicham-bab/dbt-legacy-migration-skills/migrating-stored-procedures-to-dbt"><img src="https://agentmods.dev/badge/skills/hicham-bab/dbt-legacy-migration-skills/migrating-stored-procedures-to-dbt.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.00125 | $0.03660 |
| Opus 5 | $0.00063 | $0.01830 |
| Sonnet 5 | $0.00025 | $0.00732 |
| Haiku 4.5 | $0.00013 | $0.00366 |
Grade A, and why
migrating-stored-procedures-to-dbt 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 12d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrating Stored Procedures to dbt
This skill migrates SQL stored procedures into a governed dbt project — decomposing procedural,
imperative logic into declarative ref()-based dbt models with tests, docs, and contracts, then
proving parity against the procedure's output.
The core approach: a stored procedure is a sequence of steps (build temp tables, join, filter,
aggregate, MERGE/rebuild a target). Each meaningful step becomes a dbt model in the staging →
intermediate → mart layers; the final write becomes the mart's materialization. We inventory every
procedural step, decompose it into models building on existing ref()s, and validate the final
output row-for-row against the procedure's current result table.
Success criteria: Migration is complete when:
dbt compilefinishes with 0 errors and 0 warnings- Every generated model builds (
dbt build) and its tests pass - Row-for-row (or aggregate-baseline) parity with the legacy procedure output is proven (see Step 5)
- ≥95% of the inventoried procedural steps are migrated and validated, with the residual explicitly listed for human review
Validation cost: dbt compile is the free iteration gate. Only dbt build, dbt test, and
the parity queries touch the warehouse — run those after compile is clean.
This skill shares its workflow with the legacy-to-dbt-migration-foundations skill; steps below
link into its references for the common work. Assume the migrator may be new to dbt — explain each dbt concept (materializations, incremental, snapshots, contracts, Fusion) in plain language as it comes up (foundations → dbt-concepts-explained.md), and explain the reason behind each choice, not just the mechanics.
Contents
- Additional Resources
- Migration Workflow — 8-step process with progress checklist
- Handling External Content
- Don't Do These Things
- Known Limitations & Gotchas
- Output Template for migration_changes.md
What ships with it
3 files 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.
- 12d ago First seen · 262 lines · 125 tokens per session scan A 3854fae25fa1
migrating-stored-procedures-to-dbt is a skill published in the GitHub repository hicham-bab/dbt-legacy-migration-skills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 125 tokens to every session and 3,660 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.