Borrowing it
Nothing to install: this file belongs to ROCm/aiter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ROCm/aiter/main/.claude/skills/validate-kernel-pr/SKILL.mdgit clone --depth 1 https://github.com/ROCm/aiterWrote 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/rocm/aiter/validate-kernel-pr)<a href="https://agentmods.dev/skills/rocm/aiter/validate-kernel-pr"><img src="https://agentmods.dev/badge/skills/rocm/aiter/validate-kernel-pr/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/rocm/aiter/validate-kernel-pr"><img src="https://agentmods.dev/badge/skills/rocm/aiter/validate-kernel-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.09057 |
| Opus 5.5 | $0.00029 | $0.03623 |
| Sonnet 5.5 | $0.00014 | $0.01811 |
| Haiku 4.5 | $0.00007 | $0.00906 |
Grade A, and why
validate-kernel-pr scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
'import sys,urllib.parse; print(urllib.parse.quote(sys.argv[1], safe=""))' \ How it starts
The opening of the file, as written. The whole thing — 624 lines — stays where its author put it; the contents beside it link to each section on GitHub.
validate-kernel-pr
review-pr reads the diff; it does not build and it does not run. It is a static reviewer, and a
good one — but three failure modes are invisible to it, and this skill exists for exactly those
three:
- The PR's own tests pass while the kernel is wrong. A suite whose non-aligned shapes are commented out reports green on an out-of-bounds tail store.
- A green suite that cannot fail. Loosening a comparison tolerance leaves every test passing and the kernel unguarded.
- Defects that only exist at runtime. LDS over-allocation on one arch, an accuracy gate failing against the reference, a JIT path that no-ops on cache miss.
Output is validation_report.json: deterministic execution evidence kept separate from
review-pr's advisory judgement. A review may consume it only when repo.head matches the exact
PR head; a review written without one must mark validation NOT RUN.
The two skills stay split at judgement, not at invocation. review-pr triages whether a PR has
runtime surface at all and, when it does and the PR ships a single target, runs this script itself
rather than asking a human to. Everything below is still produced here and merely consumed there:
the executor never writes an advisory verdict, and review-pr never manufactures evidence it did
not get from a report.
Invocation
The caller supplies a clean base checkout, the base-to-head patch, the exact head OID, and the test target; this script does not fetch PRs itself (see Not implemented yet).
# Example for a FlyDSL softmax PR.
REPO=ROCm/FlyDSL
PR="${PR:?set PR to the open softmax PR number}"
# 1. pin the PR identity and put its base in an isolated worktree
BASE_REF=$(gh pr view "$PR" --repo "$REPO" --json baseRefName --jq .baseRefName)
BASE_REF_PATH=$(python3 -c \
'import sys,urllib.parse; print(urllib.parse.quote(sys.argv[1], safe=""))' \
"$BASE_REF")
BASE=$(gh api "repos/$REPO/branches/$BASE_REF_PATH" --jq .commit.sha)
HEAD=$(gh pr view "$PR" --repo "$REPO" --json headRefOid --jq .headRefOid)
git worktree add --detach "/tmp/pr-$PR" "$BASE"
gh pr diff "$PR" --repo "$REPO" > "/tmp/pr-$PR.patch"
# 2. validate base and head under the same runner and GPU lock
.claude/skills/validate-kernel-pr/validate_pr.sh \
--repo "/tmp/pr-$PR" \
--patch "/tmp/pr-$PR.patch" \
--head-sha "$HEAD" \
--target tests/kernels/test_softmax.py \
--expected-route kernels.softmax_kernel:build_softmax_module \
--shape-vars M,N,dtype_str \
--shape-env ROCDSL_SOFTMAX_SHAPES \
--grid "64,2048,f32;64,2000,f32" \
--tol-table "f32=1e-5,f16=2e-3,bf16=1e-2" \
--out validation_report.json
What ships with it
18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- pick-idle-gpu.py 9.2 KB runs code
- production_scale.md 1.5 KB
- report_schema.json 32 KB
- run_script_with_probe.py 2.7 KB runs code
- scan_index_width.py 28 KB runs code
- scrape_perf.py 20 KB runs code
- shape_grid_plugin.py 4.9 KB runs code
- tests/mutants/.gitattributes 33 B
- tests/mutants/m0-clean-control.patch 372 B
- tests/mutants/m1-drop-tail-mask.patch 1.0 KB
- tests/mutants/m2-loosen-tolerance.patch 790 B
- tests/mutants/m3-vector-vs-element-index.patch 607 B
- tests/mutants/manifest.json 1.3 KB
- tests/replay_mutants.sh 4.7 KB runs code
- tests/test_validator.py 145 KB runs code
- validate_evidence.py 11 KB runs code
- validate_pr.sh 124 KB runs code
- validation_probe.py 5.6 KB runs code
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 · 624 lines · 72 tokens per session scan A 85d353a7c62c
validate-kernel-pr is a skill published in the GitHub repository ROCm/aiter (598 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 9,057 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
observability-langsmith
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
reenable-test
Guide for investigating, fixing, verifying via TDD, and re-enabling disabled or flaky Chromium tests (C++, Android Java, or WebUI). Use this skill when asked to deflake, fix, or re-enable a disabled or flaky test case, or to verify post-submit stability of a re-enabled test. Don't use for disabling a failing test…
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.