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 skills add wenyi-li/awesome-agent-kernel-skills --skill triton-cuda-debugginggit clone --depth 1 https://github.com/wenyi-li/awesome-agent-kernel-skillsWrote 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/wenyi-li/awesome-agent-kernel-skills/triton-cuda-debugging)<a href="https://agentmods.dev/skills/wenyi-li/awesome-agent-kernel-skills/triton-cuda-debugging"><img src="https://agentmods.dev/badge/skills/wenyi-li/awesome-agent-kernel-skills/triton-cuda-debugging/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/wenyi-li/awesome-agent-kernel-skills/triton-cuda-debugging"><img src="https://agentmods.dev/badge/skills/wenyi-li/awesome-agent-kernel-skills/triton-cuda-debugging.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00066 | $0.02279 |
| Opus 5 | $0.00033 | $0.01140 |
| Sonnet 5 | $0.00013 | $0.00456 |
| Haiku 4.5 | $0.00007 | $0.00228 |
Grade A, and why
triton-cuda-debugging 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 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.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 264 lines · 66 tokens per session scan A 570e05200cc7
triton-cuda-debugging is a skill published in the GitHub repository wenyi-li/awesome-agent-kernel-skills (9 stars, last pushed 3mo ago), with no licence file. It adds 66 tokens to every session and 2,279 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
triton-cuda-debugging
A troubleshooting checklist for Triton CUDA kernels, covering compilation failures, runtime errors, incorrect results, and performance problems. It includes checks for memory bounds, indexing, shapes, concurrency, and launch settings.
military-technician
A technical troubleshooting method that moves from diagnosis to analysis, repair, testing and delivery. Troubleshooting means finding the cause of a technical problem, fixing it and checking that the fix works.
error-handling
A guide to detecting and reporting errors in GPU code, especially CUDA programs. It covers checks during compilation-related setup, kernel launch, and execution.
hatch3r-bug-fix
Step-by-step bug fix workflow. Diagnose root cause, implement minimal fix, write regression test. Use when fixing bugs, working on bug report issues, or when the user mentions a bug.
hatch3r-logical-refactor
Workflow for changing behavior or logic flow without adding new features or overhauling UI. Use when modifying business logic, data flows, behavioral rules, or working on logical refactor issues.
coding
Software development, code analysis, debugging, and implementation tasks.