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 orchestration-fixergit 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/orchestration-fixer)<a href="https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/orchestration-fixer"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/orchestration-fixer/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/orchestration-fixer"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/orchestration-fixer.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.00042 | $0.06840 |
| Opus 5 | $0.00021 | $0.03420 |
| Sonnet 5 | $0.00008 | $0.01368 |
| Haiku 4.5 | $0.00004 | $0.00684 |
Grade A, and why
orchestration-fixer 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 — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration Fixer
Fix orchestration SQL files generated by SnowConvert. These files contain Snowflake task graphs (CREATE TASK) and stored procedures (CREATE PROCEDURE) that replicate ETL control flow.
Autonomous mode: When spawned as a team agent, skip all interactive stopping points, make reasonable defaults for user-facing decisions, and document assumptions in the completion report. When done, send a
send_messagetomainsummarizing your results, and respond to anyshutdown_requestwithsend_messageusingtype: "shutdown_response"andapprove: true.
Main Mode (interactive / standalone use)
Rules
- Read the reference file for an EWI/FDM code BEFORE attempting a fix
- Use
---- Start/---- Start block/---- End blocktags to locate elements, NEVER line numbers. Non-container elements (---- Start) have no closing tag — they end at the next tag. Container elements (---- Start block) have a matching---- End block. - Do NOT stop after every element — flow autonomously, pause only when genuinely blocked or needing user input
- Do NOT remove
--** SSC-FDM-*/--** SSC-EWI-*comment markers — they are documentation - DO remove
!!!RESOLVE EWI!!!marker lines when applying a fix — they break compilation - Keep the fix log updated after every fix attempt, including failures
- Record element statuses in your task artifact — the orchestrator updates
session_status.json - Valid output statuses:
test-passed,test-failed,skipped,needs-user,auto-fixed-needs-review,failed. Do NOT invent new statuses. Elements withno-fix-neededstay unchanged.
Input
This reference expects:
session_status.json— from track_status.py init (current status of each element; may includetest_environmentconfig if set viaset-test-env)ROADMAP.md— phase plan with element assignments (authored by stabilization)- The orchestration
.sqlfile path (from scan results) - Test files at
<UNIT>/stabilization/tests/orchestration/<task_procedure_name>/<element_name>.sql(generated by orchestration-test-gen) <UNIT>/stabilization/tests/orchestration/test_report.mdwith baseline results
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 · 452 lines · 42 tokens per session scan A 2ff9f7977a60
orchestration-fixer 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 42 tokens to every session and 6,840 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
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…
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
axiom-audit-grdb-performance
Use when the user mentions GRDB performance review, slow GRDB queries, app-group database setup audit, a ValueObservation that stopped updating, or pre-release GRDB scan.