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 agentmods add skills/nvidia-nemo/megatron-bridge/testingnpx skills add NVIDIA-NeMo/Megatron-Bridge --skill testinggit clone --depth 1 https://github.com/NVIDIA-NeMo/Megatron-BridgeWhat 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 | $0.00045 | $0.01544 |
| Opus 5 | $0.00023 | $0.00772 |
| Sonnet 5 | $0.00009 | $0.00309 |
| Haiku 4.5 | $0.00005 | $0.00154 |
Grade A, and why
testing 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 3d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing
Directory Layout
tests/
unit_tests/ # fast, isolated, no GPU required
functional_tests/
launch_scripts/
h100/
active/ # H100 tests that run in CI automatically
flaky/ # H100 tests quarantined from blocking CI
gb200/
active/ # GB200 tests that run in CI automatically
flaky/ # GB200 tests quarantined from blocking CI
Unit tests are independent of the launch script layout. Functional test
scripts are named {Tier}_{Description}.sh (e.g., L0_Launch_training.sh).
Tier Semantics
| Tier | Trigger | Blocking |
|---|---|---|
| L0 | Every PR, every push to main, schedule |
Yes — PR cannot merge if L0 fails |
| L1 | Push to main, schedule, PRs with needs-more-tests label |
Yes |
| L2 | Schedule, workflow_dispatch, PRs with full-test-suite label |
Yes (when triggered) |
| flaky | workflow_dispatch with test_suite=all only |
No — failures are informational |
H100 and GB200 each have independent L0/L1/L2/flaky jobs. Moving a script to
flaky/ removes it from blocking CI on that hardware target only.
Tier assignment criteria
Reserve L0 for high-risk shared paths and the smallest current set of
representative first-tier gates. L1 holds secondary but still broadly useful
coverage that runs on main, on schedules, and for opt-in PRs through the
established needs-more-tests label. Place legacy, redundant, niche,
specialized, or expensive model-family coverage in L2. Popularity alone does
not determine a test's tier; weigh risk, representativeness, cost, and overlap
with existing coverage.
Prefer unit tests over functional tests. CI GPU resources are limited; every functional test slot has a real cost.
Running Tests Locally
Unit Tests
No GPU required:
uv run pytest tests/unit_tests/ -x -v
Or inside Docker:
docker run --rm --gpus all -v $(pwd):/workdir/ -w /workdir/ megatron-bridge \
uv run pytest tests/unit_tests/
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.
- 3d ago First seen · 159 lines · 45 tokens per session scan A 5c2155982b6c
testing is a skill published in the GitHub repository NVIDIA-NeMo/Megatron-Bridge (893 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 1,544 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-08-30.
Other skills, from other repositories
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
write-tests
Write failing tests from requirements. Invoke for each todo before /implement.
dart-add-unit-test
Write and organize unit tests for functions, methods, and classes using package:test. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
myco:runtime-bootstrap-and-test-isolation
Activate this skill when adding a new manager, adding a new tool category, writing or debugging tool unit tests, diagnosing tool-visibility failures, investigating startup performance, or extending/maintaining/debugging the two-tier tool discovery system (toolindex) — even if the user doesn't explicitly ask about the…