Borrowing it
Nothing to install: this file belongs to tile-ai/tilelang-ascend. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tile-ai/tilelang-ascend/ascendc_pto/.agents/skills/tilelang-custom-skill/tilelang-debug-helper/SKILL.mdgit clone --depth 1 https://github.com/tile-ai/tilelang-ascendWrote 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/tile-ai/tilelang-ascend/tilelang-debug-helper)<a href="https://agentmods.dev/skills/tile-ai/tilelang-ascend/tilelang-debug-helper"><img src="https://agentmods.dev/badge/skills/tile-ai/tilelang-ascend/tilelang-debug-helper.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 172 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00101 | $0.01653 |
| Opus 5 | $0.00051 | $0.00826 |
| Sonnet 5 | $0.00020 | $0.00331 |
| Haiku 4.5 | $0.00010 | $0.00165 |
Grade B, and why
tilelang-debug-helper scanned grade B with 1 finding 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 7d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- GDB installed (`sudo apt install gdb`) How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TileLang Debug Helper
This skill helps you add debugging capabilities to TileLang Ascend example operators so they can be debugged with GDB in VSCode.
Overview
Debugging TileLang examples involves three main components:
- Python Debug Code: Add PID printing and wait logic to Python examples
- C++ Debug Build: Configure CMakeLists.txt to preserve debug symbols
- VSCode Configuration: Set up joint Python + C++ debugging environment
When to Use This Skill
Use this skill when:
- User asks to "debug" or "add debugging code" to a TileLang example
- User mentions GDB, breakpoints, or VSCode debugging
- User wants to step through C++ code in a TileLang operator
- User needs to inspect variables or execution flow in a TileLang kernel
- User wants to set up the complete debugging environment
Part 1: Adding Debug Code to Python Examples
Understanding the Task
When a user wants to debug a TileLang example, they need to:
- Add code to print the process ID (PID)
- Add code to wait for GDB attachment
- This allows attaching a GDB debugger to the running Python process
Step 1: Read the Original Example
First, read the example file that needs debugging. These are typically located in the examples/ directory and end with .py.
Step 2: Identify the Right Location
Find the best place to insert the debugging code. Look for:
- After imports and before the main test execution
- Before the function is called with
@tilelang.jit - After
torch.manual_seed()if present - Before the test loop starts
The goal is to pause execution before the actual kernel runs, so GDB can be attached.
Step 3: Add Debug Code
Insert a small PID-printing + input() wait snippet before kernel execution. Snippet, complete file example, and 3 common patterns (single test / multi-config / multi-function) see examples/python-debug-code.md.
Step 4: Save the Debug Version
Save the modified file. Common naming conventions:
- Add
_debugsuffix:sigmoid_debug.py - Or keep the original name if replacing it
What ships with it
5 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.
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.
- 7d ago First seen · 186 lines · 101 tokens per session scan B cf66d84ad3a5
tilelang-debug-helper is a skill published in the GitHub repository tile-ai/tilelang-ascend (363 stars, last pushed 3d ago), licensed MIT. It adds 101 tokens to every session and 1,653 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.