A guide to contributing code to Megatron Bridge through continuous integration and delivery, the automated process that checks changes before they are merged. It covers branches, signed commits, pull requests, workflow triggers, and common CI failures.

Use it to prepare commits, create pull requests, understand when CI runs, and investigate failed pipeline jobs.

It explains why a pull request's checks may not start immediately and how the project's trust and bot-driven workflow works. This prevents changes from being submitted in a form the repository will not test or accept.

cicd — Skill for Claude Code by NVIDIA-NeMo: A guide to contributing code to Megatron Bridge through…

Install

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.

agentmods

npx agentmods add skills/nvidia-nemo/megatron-bridge/cicd

Any agent

npx skills add NVIDIA-NeMo/Megatron-Bridge --skill cicd

Clone the repo

git clone --depth 1 https://github.com/NVIDIA-NeMo/Megatron-Bridge

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nvidia-nemo/megatron-bridge/cicd.svg)](https://agentmods.dev/skills/nvidia-nemo/megatron-bridge/cicd)

Your own site

<a href="https://agentmods.dev/skills/nvidia-nemo/megatron-bridge/cicd"><img src="https://agentmods.dev/badge/skills/nvidia-nemo/megatron-bridge/cicd.svg" alt="Measured on agentmods" height="20"></a>

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,530 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00029	$0.01530
Opus 5	$0.00015	$0.00765
Sonnet 5	$0.00006	$0.00306
Haiku 4.5	$0.00003	$0.00153

Measured 6d ago against content hash 78489418a1fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade C, and why

cicd scanned grade C with 1 finding 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 6d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

| Stale checkpoint auto-resume | `nemo_experiments/` from a previous run exists | `rm -rf nemo_experiments` before starting fresh |

skills/cicd/SKILL.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CI/CD

Commit and PR Workflow

Never commit directly to main — always create a feature branch.
Always sign commits: git commit -s -m "message".
PR title format: Conventional Commits — <type>(<scope>): <description> (e.g., feat(model): add Qwen3 model bridge). See @CONTRIBUTING.md for the full PR workflow, type/scope taxonomy, and DCO requirements.

How CI Is Triggered

The workflow is defined in @.github/workflows/cicd-main.yml and is triggered on push — not on pull_request. This is intentional: a bot called copy-pr-bot controls when CI runs.

Mechanism:

When a PR is opened, copy-pr-bot watches for a trust signal.
Trust is established in one of two ways:
- All commits on the PR branch are GPG-signed by a verified NVIDIA contributor → bot triggers automatically.
- An NVIDIAN posts /ok to test <commit-sha> as a PR comment → bot triggers manually for that SHA.
Once trusted, copy-pr-bot copies the PR's code into the remote branch pull-request/<number> and pushes it.
That push fires the workflow's push trigger on refs/heads/pull-request/<number>, launching CI.

Consequences:

CI never runs on untrusted pushes — external contributors always need /ok to test.
The running workflow branch is pull-request/<number>, not the author's feature branch.
Pushing a new commit to a PR does not automatically re-trigger CI unless the commit is signed or /ok to test <new-sha> is posted.
Concurrent runs for the same PR are cancelled automatically (concurrency group per PR number).

Pipeline Structure

pre-flight
  └── lint-check
        └── cicd-wait-in-queue       # queues workflows to avoid runner interleaving across PRs
              └── cicd-container-build
                    ├── unit-tests-core
                    ├── unit-tests-diffusion
                    └── functional-tests (L0 always; L1 with needs-more-tests label; L2 on schedule or full-test-suite label)

Read the full file on GitHub · 115 lines

Changes

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.

6d ago First seen · 115 lines · 29 tokens per session scan C 78489418a1fa

Subscribe to this mod's changes

cicd is a skill published in the GitHub repository NVIDIA-NeMo/Megatron-Bridge (900 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 1,530 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

CI and CD DevOps and cloud Git and workflow

import-prom-rule

Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…

ccfos/nightingale · 125 tokens

azsdk-common-pipeline-analysis

Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…

Azure/azure-sdk-for-net · 192 tokens

configure-env-variables

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…

microsoft/power-platform-skills · 119 tokens

cicd