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 vaquarkhan/data-engineering-agent-skills --skill data-platform-ci-cd-and-release-managementgit clone --depth 1 https://github.com/vaquarkhan/data-engineering-agent-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/vaquarkhan/data-engineering-agent-skills/data-platform-ci-cd-and-release-management)<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/data-platform-ci-cd-and-release-management"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/data-platform-ci-cd-and-release-management/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/vaquarkhan/data-engineering-agent-skills/data-platform-ci-cd-and-release-management"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/data-platform-ci-cd-and-release-management.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.00050 | $0.00465 |
| Opus 5 | $0.00025 | $0.00233 |
| Sonnet 5 | $0.00010 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
data-platform-ci-cd-and-release-management 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 11d 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.
What it actually says
Data Platform CI CD And Release Management
Overview
Use this skill when changes need controlled promotion across environments. It helps agents design release gates for code, contracts, infra, and datasets so teams can ship faster without losing trust.
When to Use
- adding or changing CI pipelines for data projects
- promoting changes from dev to staging to production
- releasing
dbt, orchestration, infra, or schema updates - defining rollback-aware deployment behavior
Do not treat data releases like app-only deploys. Data contracts, backfills, and environment state matter too.
Workflow
-
Identify the release surface. Include:
- code
- SQL models
- infra
- contracts
- orchestration config
- published datasets
-
Define validation gates per stage. Common gates:
- lint or formatting
- tests
- contract validation
- sample or shadow runs
- reconciliation
-
Separate deployment from publish where needed.
-
Make rollback and forward-fix expectations explicit.
-
Record release ownership and approval points for high-risk changes.
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "If tests pass, the data release is safe." | Data releases often need contract, reconciliation, and environment checks too. |
| "We can deploy and publish in one step." | Deployment and downstream visibility should not always be coupled. |
| "Rollback is easy because Git exists." | Rollback for data state and published outputs is often harder than code rollback. |
Red Flags
- environment promotion rules are unclear
- releases do not separate code success from publish safety
- rollback is mentioned but not operationally real
- high-risk changes have no staged validation
Verification
- Release surfaces and environment boundaries are explicit
- Validation gates exist for the change type
- Publish behavior is controlled where needed
- Rollback or forward-fix expectations are documented
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.
- 11d ago First seen · 67 lines · 50 tokens per session scan A 37f7a73b8510
data-platform-ci-cd-and-release-management is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (45 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 465 once invoked, about $0.0003 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-30.
Other skills, from other repositories
lov-release-via-cicd
A release workflow for Node, Tauri, Vite, shell, and GitHub Release projects. It checks or configures automated versioning and publishing, including macOS signing and notarisation when relevant.
ci-cd-pipelines
When designing GitHub Actions workflows, optimizing pipeline speed, implementing deployment gates.
npm-trusted-publishing
Use when setting up npm publishing with GitHub Actions - provides trusted publishing with OIDC, provenance attestations, and monorepo configuration.
production-release-gating
Stop every push/merge to main from shipping to production — deploy only on a real release. Use when a merge to main unexpectedly deploys to prod, when you want production to deploy only on a semantic-release version (not every commit), when setting up preview-on-feature-branch but gated-prod-on-main, wiring a Vercel…
cosmosmith-devops-release
Prepare build, CI, environment, deployment, monitoring, rollback, and release readiness for a Cosmosmith project. Use when tasks approach release, when setup/deploy commands are missing, or when current platform docs are needed.
deployment-composer
Compose deployment workflows from smaller skills and repo signals, including trunk-based releases, CI quality gates, provider deployment, post-deploy verification, rollback, and failed-check diagnosis. Use when the user asks for a deployment plan, release workflow, ship-to-staging/production environments, or a smart…