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 Ascend/agent-skills --skill atb-debug-guidegit clone --depth 1 https://github.com/Ascend/agent-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/ascend/agent-skills/atb-debug-guide)<a href="https://agentmods.dev/skills/ascend/agent-skills/atb-debug-guide"><img src="https://agentmods.dev/badge/skills/ascend/agent-skills/atb-debug-guide/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/ascend/agent-skills/atb-debug-guide"><img src="https://agentmods.dev/badge/skills/ascend/agent-skills/atb-debug-guide.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.00073 | $0.02801 |
| Opus 5.5 | $0.00029 | $0.01120 |
| Sonnet 5.5 | $0.00015 | $0.00560 |
| Haiku 4.5 | $0.00007 | $0.00280 |
Grade A, and why
atb-debug-guide 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 1mo 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
Licensed MulanPSL-2.0
The repository is licensed MulanPSL-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 1mo ago First seen · 351 lines · 73 tokens per session scan A 1811bcff7e30
atb-debug-guide is a skill published in the GitHub repository Ascend/agent-skills (51 stars, last pushed 5mo ago), licensed MulanPSL-2.0. It adds 73 tokens to every session and 2,801 once invoked, about $0.0003 per session on Opus 5.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
external-gitcode-ascend-atb-debug-guide
A troubleshooting guide for ATB operator tests and Ascend NPU environments. It covers issues such as ABI mismatches, memory errors, failed CSV tests, and ACLNN interface problems.
external-gitcode-ascend-atb-aclnn-operator-migration
A migration workflow for moving ATB operators to ACLNN, Ascend's operator library interface. It handles parameter mapping, runner implementation, device-based switching, and functional and performance checks.
external-gitcode-ascend-ascend-transformer-boost
An index of skills for developing and deploying Huawei's Ascend Transformer Boost library, a set of tools for accelerating transformer-based AI models. It covers the main stages of working with Ascend NPUs and related operator libraries.
fix
Structured bug fix — reproduce (failing test), diagnose, fix (minimal change), verify, commit. Enforces test-first. Use when a bug needs a methodical fix.
Debugging Strategies
Advanced debugging patterns for test failures covering root cause analysis, flakiness investigation, performance debugging, and systematic troubleshooting methodologies.
debug
Use when something is broken — a failing or flaky test, crash, wrong result or regression — and the root cause must be reproduced and proven before any fix. On-demand; callable mid-implement. NOT a feature to spec or build (that is specify/implement), NOT the lint/test gate (that is verify), NOT adversarial diff…