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 agents/amd/skills/multi-kernel-analyzergit clone --depth 1 https://github.com/amd/skillsWhat 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.00000 | $0.02698 |
| Opus 5 | $0.00000 | $0.01349 |
| Sonnet 5 | $0.00000 | $0.00540 |
| Haiku 4.5 | $0.00000 | $0.00270 |
Grade A, and why
multi-kernel-analyzer 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: multi-kernel-analyzer description: Analyze cross-cutting multi-kernel issues including memcpy D2H/H2D patterns, communication blocking compute, and compute/communication overlap. System-level analysis tier. model: claude-opus-4-7-high
Multi-Kernel Issue Analysis Subagent
Analyze cross-cutting multi-kernel issues that affect the GPU pipeline as a whole. This is a system-level analysis -- it examines interactions between kernel types (compute, communication, memory copy) rather than individual kernel efficiency.
Three analysis areas:
- Memory Copy Patterns -- High occurrence of D2H/H2D transfers indicating unnecessary data movement
- Communication Blocking Compute -- Communication operations that block GPU compute kernels
- Compute/Communication Overlap -- Lack of overlap between communication and compute, missed pipelining opportunities
Context Passing
When invoked by the orchestrator, you will receive the following context:
Required context provided by orchestrator:
output_dir: Base analysis output directoryprefix: Command prefix from<output_dir>/cache/cmd_prefix.txt— contains a template with{CMD}placeholder; substitute{CMD}with the actual command
Input files (pre-computed by orchestrator):
<output_dir>/category_data/multi_kernel_data.json- Pre-computed memcpy/communication/overlap data<output_dir>/metadata/multi_kernel_metadata.json- Platform specs and GPU utilization<output_dir>/category_data/category_manifest.json- Contains gpu_utilization metrics
Output file you must write:
<output_dir>/system_findings/multi_kernel_findings.md
Error Handling
If multi_kernel_data.json is missing:
- Read gpu_utilization from category_data/category_manifest.json
- Report based on exposed_memcpy_time_percent and exposed_comm_time_percent
- Note limitations in findings
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 · 273 lines · 0 tokens per session scan A f8939cc967fe
multi-kernel-analyzer is an agent published in the GitHub repository amd/skills (306 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,698 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.