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/rocm/aiter/opus-kernel-best-practicenpx skills add ROCm/aiter --skill opus-kernel-best-practicegit clone --depth 1 https://github.com/ROCm/aiterWhat 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.00046 | $0.03152 |
| Opus 5 | $0.00023 | $0.01576 |
| Sonnet 5 | $0.00009 | $0.00630 |
| Haiku 4.5 | $0.00005 | $0.00315 |
Grade A, and why
opus-kernel-best-practice 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 2d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPUS Kernel Compile-Time Best Practices
Techniques for reducing HIP/C++ kernel compile time when using opus.hpp. These patterns were developed while optimizing a GQA flash attention kernel from 4.8s to 1.5s (70% reduction) in device-only compilation.
Required headers and include paths
For kernel development with OPUS, use these headers from csrc/include/:
opus/opus.hpp— the OPUS template library + device intrinsic wrappers. This is the only include needed for device code. Providesopus::thread_id_x(),opus::block_id_x(),opus::sync_threads(),opus::warp_all(), etc.opus/hip_minimal.hpp— minimal HIP host-side only declarations (dim3,hipMalloc,hipLaunchKernelGGL, etc.). Use on the host pass instead of<hip/hip_runtime.h>.
hipcc my_kernel.cu -I<aiter_root>/csrc/include -D__HIPCC_RTC__ -std=c++20 -O3 --offload-arch=gfx950
| HIP runtime | opus:: wrapper | LLVM builtin |
|---|---|---|
threadIdx.x |
opus::thread_id_x() |
__builtin_amdgcn_workitem_id_x() |
blockIdx.x |
opus::block_id_x() |
__builtin_amdgcn_workgroup_id_x() |
blockDim.x |
opus::block_size_x() |
__builtin_amdgcn_workgroup_size_x() |
gridDim.x * blockDim.x |
opus::grid_size_x() |
__builtin_amdgcn_grid_size_x() |
__syncthreads() |
opus::sync_threads() |
__builtin_amdgcn_s_barrier() |
__all(pred) |
opus::warp_all(pred) |
— |
If anything is missing, contact the maintainer ([email protected]) for adding support.
0. Always Separate Device and Host Code (Most Important)
This is the single most impactful technique. hipcc always performs two compilation passes on every .hip/.cu file — one for the host (x86_64) and one for the device (AMDGPU). The heavy opus.hpp template library is only needed on the device side, but without a guard, hipcc parses it on BOTH passes, doubling the frontend cost.
Always structure your kernel files like this:
// my_kernel.cu
#ifdef __HIP_DEVICE_COMPILE__
// ── Device pass: include opus.hpp and define kernels ──
#include "opus/opus.hpp"
__global__ __launch_bounds__(256, 2)
void my_kernel(const float* src, float* dst, int n) {
// ... opus layout, load, store, MMA, etc.
}
#else
// ── Host pass: minimal declarations + launcher only ──
#include "opus/hip_minimal.hpp"
__global__ void my_kernel(const float* src, float* dst, int n); // declaration only
extern "C" void run_my_kernel(const void* d_src, void* d_dst, int n) {
dim3 grid((n + 255) / 256), block(256);
hipLaunchKernelGGL(my_kernel, grid, block, 0, 0,
(const float*)d_src, (float*)d_dst, n);
hipDeviceSynchronize();
}
#endif
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.
- 2d ago First seen · 275 lines · 46 tokens per session scan A 75af29fc86fd
opus-kernel-best-practice is a skill published in the GitHub repository ROCm/aiter (543 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 3,152 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.