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 sainteye/clawdline --skill evidence-debugginggit clone --depth 1 https://github.com/sainteye/clawdlineWrote 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/sainteye/clawdline/evidence-debugging)<a href="https://agentmods.dev/skills/sainteye/clawdline/evidence-debugging"><img src="https://agentmods.dev/badge/skills/sainteye/clawdline/evidence-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/sainteye/clawdline/evidence-debugging"><img src="https://agentmods.dev/badge/skills/sainteye/clawdline/evidence-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.00044 | $0.00452 |
| Opus 5.5 | $0.00018 | $0.00181 |
| Sonnet 5.5 | $0.00009 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
evidence-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 today.
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
Evidence-led debugging
Find the failing boundary before choosing a fix. Apply the current task and repository rules, including the existing targeted check gate and shared-tree ownership. This skill grants no permission to install, dispatch, deploy, spend, or restart anything.
- Record the trigger, expected behavior, actual behavior, and exact revision or running version. Read the real error and nearby code. If reproduction is intermittent, preserve that uncertainty and gather evidence rather than naming a cause from one failure.
- Follow the value or operation through its callers and component boundaries. For sends and stalls, distinguish acceptance, execution, delivery, observation, and acknowledgement; inspect queue bounds, retries, receipts, resume and failure isolation. Inspect only task-relevant state and redact secrets from diagnostics.
- State a falsifiable hypothesis and the observation that would disprove it. Compare a working path or version when available; vary one cause at a time. Repeated unsuccessful patches are a reason to revisit the model of the system, not stack another timeout on it.
- Fix at the earliest responsible boundary with the smallest sufficient change. For behavioral fixes, prove a focused reproduction fails without the fix and succeeds with it, in an isolated tree. Use the repository's existing local gate; broader checks remain governed by project policy.
- Report the observed cause, correction, evidence and remaining uncertainty. Keep temporary mitigation distinct from a verified fix. Continue authorized work without adding approval checkpoints for routine implementation choices.
Keep invocation and verification evidence in the normal Session history. If the current project has an approved workflow pilot, follow its own checkpoint and evidence limits. Do not start separate model calls to evaluate the skill during ordinary work.
Adapted from obra/superpowers systematic-debugging at commit 2ce8aa15d05bd57213e6f746f953aafb7ded7a8b. Copyright (c) 2025 Jesse Vincent, MIT. Clawdline-specific workflow and permission boundaries are local adaptations.
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.
- today First seen · 19 lines · 44 tokens per session scan A 12bf03169a4a
evidence-debugging is a skill published in the GitHub repository sainteye/clawdline (1 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 452 once invoked, about $0.0002 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-10-30.
Other skills, from other repositories
burrow-system-tools
Diagnose and fix the user's Mac with Burrow's local MCP tools (burrowdoctor, burrowsnapshot, burrowtopprocesses, burrowprocessusage, burrowports, burrowanalyze, burrowdiskforecast, burrowdupes, burrowanomalies, burrowagentaudit, burrowclean, …). Use whenever the Mac is slow, hot, loud, low on disk, draining battery…
doca-debug
Use this skill when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca symbol, a runtime call returning DOCAERROR, a silent service or tool, or a stack trace / valgrind / core dump — and needs the layered ladder (install → version → build → link → runtime →…
doca-flow
DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Also covers pipe validation…
compute-sanitizer-diagnose-cuda-bugs
Detect and diagnose CUDA correctness bugs with NVIDIA Compute Sanitizer. Routes GPU memory errors, shared-memory data races, uninitialized-memory reads, and synchronization/barrier bugs to the right sub-tool (memcheck, racecheck, initcheck, synccheck) and explains how to build, run, and read the report. Use when…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
doca-dpa-hl-tracer
Use this skill when the user runs docadpahltracer to capture/decode DPA-side traces at the programming-events layer (kernel entry/exit, sync points, comm primitive calls, RDMA WR submission, completion drain) — picking TRACE vs CRIT, tuning the JSON config (file-size limits + filesizelimitpolicy, thread…