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 instructions/rocm/aiter/aiter-ops-tritongit 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/instructions/rocm/aiter/aiter-ops-triton)<a href="https://agentmods.dev/instructions/rocm/aiter/aiter-ops-triton"><img src="https://agentmods.dev/badge/instructions/rocm/aiter/aiter-ops-triton.svg" alt="Measured on agentmods" 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 | $0.03060 | $0.03060 |
| Opus 5 | $0.01530 | $0.01530 |
| Sonnet 5 | $0.00612 | $0.00612 |
| Haiku 4.5 | $0.00306 | $0.00306 |
Grade A, and why
aiter aiter-ops-triton.instructions.md 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 4d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AITER Triton ops — PR review rules
When a change violates one of these rules, flag it and point the author to the relevant rule — reviewers may not know these conventions yet.
Reuse before adding
Always prefer reusing existing code over adding new code. Before a PR adds a
helper, kernel, or utility, the existing ones should have been checked:
utils/ (config loading, shuffling, arch info, logging, kernel_repr),
_triton_kernels/common/ (shared split-K reduce), and existing kernels and
test helpers. Flag new code that duplicates functionality already in the
tree, even partially — the fix is to extend or import the existing
implementation, not to add a parallel copy.
Folder structure and imports
The layout is: public wrapper modules in category folders
(gemm/{basic,batched,feed_forward,fused}/, attention/, moe/,
normalization/, quant/, rope/, fusions/, comms/, conv/,
gated_delta_net/, kimi_delta_attn/, gluon/), kernel bodies under
_triton_kernels/ at the same relative category path, or under
_gluon_kernels/<arch>/ at the same relative category path when the Gluon
implementation is architecture-specific. Shared machinery lives in utils/
and tuned JSON in configs/. Flag:
- New modules added flat at the top of
aiter/ops/triton/— every new wrapper goes in the correct category folder. - New launchable
@triton.jitor@gluon.jitkernel bodies defined inside public wrapper modules — Triton bodies belong under_triton_kernels/and Gluon bodies under_gluon_kernels/<arch>/, mirroring the wrapper's category path. JIT-decorated device helpers that are called only from another kernel may remain with the entry kernel they support. - Generic helpers (config loading, shuffling, arch detection, logging)
re-implemented inside a kernel file instead of imported from
utils/. - New code importing via the legacy flat paths
(
from aiter.ops.triton.gemm_a16w16 import ...) — the categorized path is required;_BACKWARD_COMPAT_MAPexists only for old external callers. - Relative imports (
from .foo import ...,from ..utils import ...) — only absolute imports (from aiter.ops.triton.<...> import ...) are allowed.
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.
- 4d ago First seen · 229 lines · 3,060 tokens per session scan A 34ddae0cbd88
aiter aiter-ops-triton.instructions.md is an instructions file published in the GitHub repository ROCm/aiter (543 stars, last pushed 4d ago), licensed MIT. It adds 3,060 tokens to every session, about $0.0153 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.