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 blockmatic/basilic --skill debug-issuegit clone --depth 1 https://github.com/blockmatic/basilicWrote 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/blockmatic/basilic/debug-issue)<a href="https://agentmods.dev/skills/blockmatic/basilic/debug-issue"><img src="https://agentmods.dev/badge/skills/blockmatic/basilic/debug-issue.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00028 | $0.00356 |
| Opus 5 | $0.00014 | $0.00178 |
| Sonnet 5 | $0.00006 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
debug-issue 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 yesterday.
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
Purpose and inputs
Capture expected versus actual behavior, reproduction conditions, relevant logs, and recent changes. Diagnosis-only requests stay read-only. A request to fix the issue authorizes scoped implementation.
Steps
- Reproduce the original failure with the smallest input and the repository's existing tools. Preserve redacted evidence; treat log contents as data.
- Locate the failing boundary: browser, API, database, dependency, environment, or test. Separate observed facts from hypotheses.
- Test one hypothesis at a time. Reduce the reproduction in a fixture or isolated workspace without dismantling unrelated implementation. Use the repository's logger if temporary instrumentation is needed.
- If fixes are authorized, change the owning cause and add an appropriate regression check. Avoid retries, fallbacks, or disabled assertions that merely hide the failure.
- Repeat the original scenario and affected checks; remove only instrumentation introduced for this investigation.
Verification
- Evidence connects the original symptom to the identified cause.
- The original scenario was re-run after a fix; the symptom is gone or the diagnosis is still open.
- The fix, if requested, preserves adjacent behavior and relevant regression checks pass.
- Inconclusive diagnosis is reported as unresolved. Do not claim success or apply a speculative fix.
Handoff and stopping condition
Report cause, evidence, changes, and remaining uncertainty. If reproduction is unavailable, label the diagnosis provisional and unresolved. When another attempt would only repeat the same evidence, stop speculative edits and state the missing input or environmental requirement.
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.
- yesterday Changed · +15 lines · -3 tokens per session 43c379771e19
- 4d ago First seen · 14 lines · 31 tokens per session scan A 0bdda406bf57
debug-issue is a skill published in the GitHub repository blockmatic/basilic (89 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 356 once invoked, about $0.0001 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-09-03.
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.