neycyanshi

Moe Swarm โ€” Development skill for Claude Code

Development community

Claude Code agents that optimize CUDA/Triton kernels.

How to install Moe Swarm

This entry records only its repository, not the path inside it, so there is no exact command to give. Open neycyanshi/moe-swarm and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Moe Swarm does

Claude Code agents that optimize CUDA/Triton kernels. DeepSeek-V3 FP8 MoE: 3.17x faster than FlashInfer's CUTLASS.

Alternatives in Development

  • Claude Code Rust โ€” ๐Ÿš€ Rust ๅ…จ้‡้‡ๆž„็š„ Claude Code - ๆ€ง่ƒฝๆๅ‡ 2.5x๏ผŒไฝ“็งฏๅ‡ๅฐ‘ 97% High-performance Rust implementation of Claude Code with 2.5x f 1.4k โ˜…
  • Claude Flow Swarm 625 โ˜…
  • Swarm Collect โ€” Collect and synthesize results from a completed swarm 508 โ˜…

README

MoE-Swarm

Claude Code agents that optimize CUDA/Triton kernels. DeepSeek-V3 FP8 MoE: 3.17x faster than FlashInfer's CUTLASS.

Seven agents per round compete on the FP8 fused-MoE layer of DeepSeek-V3, on one NVIDIA H200. The speedup over `cutlass_fused_moe` is averaged over the 19 workloads of the [MLSys 2026 FlashInfer contest](https://github.com/flashinfer-ai/flashinfer-bench) (Track A), all 19 correct.

The repo holds the agent harness and the kernel it produced. The harness is built around this one kernel's spec; pointing it at another kernel means writing a new spec and roofline model for it.

Per-workload speedup over FlashInfer cutlass_fused_moe on H200: 6.94x at T=1, 2.4-5.4x for T=7 to 80, 2.15x at T=901, 3.15x and 3.00x for the two prefill workloads; mean 3.17x

Speedup is the mean of `baseline_latency / our_latency` over the 19 workloads, measured on one H200 with the SM clock locked at 1400 MHz. The contest's own baseline (TRT-LLM) runs only on Blackwell, so these numbers are not comparable with the contest leaderboard. On the largest prefill workload the call drops from 2383 to 1580 ยตs, with both GEMMs above 1 PFLOP/s.

Where the speed came from:

step score what changed
PyTorch port of the reference 0.13ร— dequantizes each expert's weights to bf16 before every matmul
Triton kernel, first agent rounds 2.84ร— FP8 weights read from HBM once, no dequantized copy, fused SwiGLU and combine, no host syncs, CUDA graph
three more agent rounds 3.01ร— launch overhead, tile shapes, the combine epilogue
hand-written CUDA prefill path 3.17ร— warp-specialized TMA + wgmma for T โ‰ฅ 512

Most of the gain is the first jump, and it is about memory traffic. Before every matmul, v1 converted each active expert's FP8 weights into a bf16 copy in HBM: 1 byte read, 2 bytes writte