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 orchestra-hq/orchestra-skills --skill fix-pipeline-dbt-taskgit clone --depth 1 https://github.com/orchestra-hq/orchestra-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/orchestra-hq/orchestra-skills/fix-pipeline-dbt-task)<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/fix-pipeline-dbt-task"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/fix-pipeline-dbt-task/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/orchestra-hq/orchestra-skills/fix-pipeline-dbt-task"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/fix-pipeline-dbt-task.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.00103 | $0.01863 |
| Opus 5.5 | $0.00041 | $0.00745 |
| Sonnet 5.5 | $0.00021 | $0.00373 |
| Haiku 4.5 | $0.00010 | $0.00186 |
Grade A, and why
fix-pipeline-dbt-task 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix → validate on a branch → confirm → merge. Narrate each step briefly, like a data engineer. Never print secrets/tokens.
0. Access
MCP is preferred but optional. If the Orchestra MCP tools aren't present, use the public REST API directly with $ORCHESTRA_API_KEY (check the env — it's often already set). For git, $GITHUB_TOKEN is usually set too.
If neither MCP nor a key is available, point the user at the Orchestra MCP setup docs (https://docs.getorchestra.io/docs/mcp) or ask for an API key, then stop.
Base: https://app.getorchestra.io/api/engine/public — header Authorization: Bearer $ORCHESTRA_API_KEY.
1. Inputs from identify-pipeline-error
identify-pipeline-error hands you: the pipeline run ID (RID), pipeline ID (PID), the failed dbt task run ID (TRID), integration=DBT_CORE, the run branch/commit, the task's taskParameters, and the cause classification (a dbt code/config issue). Use them directly — don't re-run the identification.
If invoked standalone (no handoff): run identify-pipeline-error first, or do its minimum yourself — GET /pipeline_runs?pipeline_run_ids=<RID> then GET /task_runs?pipeline_ids=<PID>&page_size=50 (filter to this RID client-side; the pipeline_run_ids filter does not work on /task_runs, 7-day window) to find the FAILED dbt task.
Capture taskParameters exactly — especially branch, commands, project_dir, use_state_orchestration. These are run inputs you must preserve on retry. The pipeline run's branch is where the Orchestra YAML lives; the dbt clone branch is a separate task param (commonly an input like dbt_branch).
Pull the logs you'll fix against:
GET /pipeline_runs/<RID>/task_runs/<TRID>/logs # list filenames
GET /pipeline_runs/<RID>/task_runs/<TRID>/logs/download?filename=1/debug_task # URL-encode spaces, e.g. 1/dbt%20run
debug_task = dbt debug (config/YAML validation); dbt run / dbt build = compile + execution.
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 · 96 lines · 103 tokens per session scan A b6107b3732a0
fix-pipeline-dbt-task is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 1,863 once invoked, about $0.0004 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-09-09.
Other skills, from other repositories
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
enable-check-includes-strict
Enable and migrate Chromium targets and directories to checkincludesstrict = true, diagnosing and resolving header include violations as part of the checkincludesstrict LSC. Use when adding directories to the allowlist, enabling strict header checks on targets, or resolving CHECKINCLUDESSTRICTUNTRIAGED targets.
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
gsd-audit-fix
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit.
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
stage-payload-reverts
Create TRT JIRA bugs, open revert PRs, and trigger payload jobs for high-confidence revert candidates.