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 sonature-lab/timsquad --skill tsq-debugginggit clone --depth 1 https://github.com/sonature-lab/timsquadWrote 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/sonature-lab/timsquad/tsq-debugging)<a href="https://agentmods.dev/skills/sonature-lab/timsquad/tsq-debugging"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/tsq-debugging/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/sonature-lab/timsquad/tsq-debugging"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/tsq-debugging.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.00067 | $0.00663 |
| Opus 5.5 | $0.00027 | $0.00265 |
| Sonnet 5.5 | $0.00013 | $0.00133 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
tsq-debugging 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.
What it actually says
Systematic Debugging
체계적 디버깅을 통해 근본 원인(root cause)을 빠르게 찾고 재발을 방지하는 방법론.
Philosophy
- 증상이 아닌 근본 원인을 찾는다
- 가설을 세우고 실험으로 검증한다 (추측으로 코드를 수정하지 않는다)
- Defense in depth — 같은 유형의 버그가 재발하지 않도록 방어 계층을 추가한다
Resources
| Priority | Type | Resource | Description |
|---|---|---|---|
| HIGH | ref | root-cause-tracing | 5 Whys + 가설-실험 루프 상세 가이드 |
Quick Rules
Debugging Loop
- Reproduce — 버그를 100% 재현하는 최소 조건 확보
- Hypothesize — 원인 가설을 1~3개 세우고 가능성 순으로 정렬
- Test — 각 가설을 실험으로 검증 (로그 추가, breakpoint, 입력 변경)
- Fix — 근본 원인 수정 (증상 대응 X)
- Verify — 원래 재현 조건에서 버그 사라짐 확인
- Prevent — 회귀 테스트 추가, 방어 로직 보강
Root Cause Categories
| 카테고리 | 예시 |
|---|---|
| State | 예기치 않은 상태 변이, race condition |
| Data | 잘못된 입력, null/undefined, 타입 불일치 |
| Logic | 잘못된 조건, off-by-one, 순서 오류 |
| Environment | 설정 차이, 의존성 버전, OS 차이 |
| Integration | API 응답 변경, 타이밍, 네트워크 |
Anti-Patterns
- Shotgun debugging: 여러 곳을 동시에 수정 → 원인 특정 불가
- Print-and-pray: console.log만 추가하고 가설 없이 실행 반복
- Blame game: "내 코드 문제 아닌데" → 증거 없이 외부 원인 지목
Checklist
| Priority | Item |
|---|---|
| CRITICAL | 재현 조건이 명확한가 |
| CRITICAL | 가설을 세운 후 수정했는가 (추측 수정 X) |
| HIGH | 근본 원인을 찾았는가 (증상 대응만 하지 않았는가) |
| HIGH | 회귀 테스트를 추가했는가 |
| MEDIUM | 같은 유형의 버그를 방지하는 방어 로직이 있는가 |
What ships with it
1 file 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.
- 1mo ago First seen · 61 lines · 67 tokens per session scan A c8bf9acbb41c
tsq-debugging is a skill published in the GitHub repository sonature-lab/timsquad (12 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 663 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
seedance-troubleshoot
This skill should be used when a Seedance 2.0 output is blurry, jittery, off-prompt, morphing, blocked, visually generic, unstable, desynced, inconsistent, or otherwise fails and needs root-cause diagnosis.
cml-packet-capture
CML packet capture — start, stop, download pcaps from CML lab links, integrate with Packet Buddy for analysis. Use when capturing packets in a CML lab, troubleshooting BGP or OSPF with packet analysis, or downloading pcap files for Wireshark review.
k8s-service-path
Trace the Kubernetes service path — Service to selector to pods to EndpointSlices to readiness, plus Ingress routing. Use when a service is getting no traffic, an ingress is not routing, or someone asks why a workload is unreachable inside a cluster.
te-path-analysis
Cisco ThousandEyes — path visualization, BGP route analysis, outage investigation, instant tests, endpoint agent diagnostics. Requires ThousandEyes endpoint/enterprise agents already deployed. Use when tracing network paths hop-by-hop, investigating why a site is slow, analyzing BGP route changes, diagnosing an…
packet-analysis
Analyze network packet captures (.pcap/.pcapng) using Packet Buddy MCP. Use when opening a pcap file, inspecting packet captures, troubleshooting network traffic, analyzing retransmissions, or filtering packets by protocol.
k8s-workload-inventory
List Kubernetes workloads and namespaces — pods with their node, phase and readiness, plus events. Use when asked what is running, where it is running, what is failing, or for a general inventory of a cluster.