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/vipshop/cache-dit/cute-dsl-kernelnpx skills add vipshop/cache-dit --skill cute-dsl-kernelgit clone --depth 1 https://github.com/vipshop/cache-ditWrote 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/vipshop/cache-dit/cute-dsl-kernel)<a href="https://agentmods.dev/skills/vipshop/cache-dit/cute-dsl-kernel"><img src="https://agentmods.dev/badge/skills/vipshop/cache-dit/cute-dsl-kernel.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.00063 | $0.02561 |
| Opus 5 | $0.00032 | $0.01281 |
| Sonnet 5 | $0.00013 | $0.00512 |
| Haiku 4.5 | $0.00006 | $0.00256 |
Grade A, and why
cute-dsl-kernel 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 3d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write a CuTe DSL GPU Kernel
Goal
Use the bundled CuTe DSL API snapshots in this skill and the workspace CUTLASS checkout to design, implement, debug, and integrate CuTe DSL GPU kernels in a way that is reusable across projects, including cache-dit.
When to Use
Use this skill when you need to:
- write or modify a CuTe DSL GPU kernel in Python
- study CuTe DSL types, runtime helpers, architecture APIs, or pipeline abstractions
- port or rewrite an existing CUDA or C++ operator into CuTe DSL
- use CuTe DSL examples from the workspace CUTLASS checkout as reference material
- debug CuTe DSL compilation, runtime behavior, layout issues, or integration problems
Do not use this skill for:
- CUTLASS or CuTe C++ template work as the primary task; use
cutlass-cpp-kernel - generic CUDA/PTX documentation lookup with no CuTe DSL angle; use
cuda-cpp-kernel - repository integration plumbing by itself; pair with
operator-migration
Core Rule
Read the relevant API reference files before writing kernel code.
Do not guess CuTe DSL APIs or architecture helpers from memory when the bundled docs or workspace CUTLASS examples can answer the question precisely.
Reference Style Rule
Use Copilot-friendly sibling-file references for bundled docs in this skill, for example:
cute.mdcute_runtime.mdutils.mdcute_nvgpu_tcgen05.mdpipeline.md
Use workspace-relative paths for CUTLASS sources, for example:
vipshop/cutlass/python/CuTeDSL/vipshop/cutlass/examples/python/CuTeDSL/vipshop/cutlass/python/pycute/vipshop/cutlass/include/cute/vipshop/cutlass/media/docs/pythonDSL/
Do not use agent-specific skill paths or placeholder-driven argument text in the final skill content.
Read These Files First
Core API references:
cute.md— core CuTe DSL types and tensor or layout operationscute_runtime.md— runtime helpers and data interoputils.md— helper utilities and hardware info
Architecture-specific references:
What ships with it
21 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- cute_arch.md 42 KB
- cute_nvgpu_common.md 9.3 KB
- cute_nvgpu_cpasync.md 9.5 KB
- cute_nvgpu_tcgen05.md 20 KB
- cute_nvgpu_warp.md 4.9 KB
- cute_nvgpu_warpgroup.md 5.0 KB
- cute_nvgpu.md 285 B
- cute_runtime.md 15 KB
- cute.md 142 KB
- intro.md 86 KB
- kernel-templates.md 21 KB
- pipeline.md 52 KB
- sm100-optimization-guide.md 24 KB
- sm103-optimization-guide.md 18 KB
- sm120-optimization-guide.md 26 KB
- sm89-optimization-guide.md 21 KB
- sm90-optimization-guide.md 10 KB
- troubleshooting.md 6.4 KB
- utils_sm100.md 16 KB
- utils_sm90.md 5.2 KB
- utils.md 61 KB
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.
- 3d ago First seen · 221 lines · 63 tokens per session scan A e5174ee2b403
cute-dsl-kernel is a skill published in the GitHub repository vipshop/cache-dit (1,262 stars, last pushed 6d ago), licensed Apache-2.0. It adds 63 tokens to every session and 2,561 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-08-30.
Other skills, from other repositories
bump-dependency
Bumps a Python package dependency across Home Assistant Core integrations, regenerates core requirement files, runs verification tests and prek lint, and prepares a pull request with proper release/compare links.
agent-framework-azure-ai-py
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.
datamodel-code-generator
Use this skill when the user wants Python data models, Pydantic models, dataclasses, TypedDicts, msgspec structs, or type-safe Python classes generated from OpenAPI, AsyncAPI, JSON Schema, GraphQL, JSON/YAML/CSV sample data, MCP tool schemas, Protocol Buffers, XML Schema, Apache Avro, or existing Python model objects.…