What is sentinel-dv-failure-debugging?

A tool for investigating one failed SystemVerilog, UVM, or cocotb test. It uses recorded test, failure, timeline, and waveform evidence to build a possible cause.

Use it to explain why a test failed, identify evidence for the cause, determine how to reproduce it, and keep ambiguous test matches separate until the right one is known.

The final error message is not always the first or real cause of a failure. The tool helps distinguish build, assertion, protocol, scoreboard, timeout, and infrastructure problems.

How kiranreddi/sentinel-dv configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to kiranreddi/sentinel-dv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/kiranreddi/sentinel-dv/main/.agents/skills/sentinel-dv-failure-debugging/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/kiranreddi/sentinel-dv

Made for: Claude Code, Codex.

Or install sentinel-dv, the plugin that ships this one along with the rest of its 3 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/kiranreddi/sentinel-dv/sentinel-dv-failure-debugging/github.svg)](https://agentmods.dev/skills/kiranreddi/sentinel-dv/sentinel-dv-failure-debugging)

Your own site

<a href="https://agentmods.dev/skills/kiranreddi/sentinel-dv/sentinel-dv-failure-debugging"><img src="https://agentmods.dev/badge/skills/kiranreddi/sentinel-dv/sentinel-dv-failure-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/kiranreddi/sentinel-dv/sentinel-dv-failure-debugging"><img src="https://agentmods.dev/badge/skills/kiranreddi/sentinel-dv/sentinel-dv-failure-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 799 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00070	$0.00799
Opus 5	$0.00035	$0.00400
Sonnet 5	$0.00014	$0.00160
Haiku 4.5	$0.00007	$0.00080

Measured 10d ago against content hash f518206b59f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

sentinel-dv-failure-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 10d 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.

.agents/skills/sentinel-dv-failure-debugging/SKILL.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sentinel DV Failure Debugging

Build a causal explanation for one test from bounded indexed evidence. Do not mistake the last or loudest message for the initiating failure.

Inputs

Accept a test_id, a logical test name plus run or suite context, or a failure description that can be resolved with tests.list. Keep ambiguous matches separate until the user or evidence selects one.

Preflight

Confirm the Sentinel DV tools are available with tests.list using page=1.
If unavailable, report that the Sentinel DV MCP server must be configured and the relevant artifacts indexed.

Workflow

Resolve the test using supported tests.list filters: run_id, framework, status, and name_pattern. Keep multiple matches separate by test_id.
Call tests.get for execution context such as run, framework, seed, simulator, DUT top, status, and duration. It does not supply artifact references.
Read every relevant page from failures.list with test_id and include_evidence=true. The API returns newest events first; collect pages, then sort known time_ns values ascending before causal analysis. Keep untimed events explicitly separate.
Read every relevant page from assertions.failures for the same test. Resolve important assertion definitions with assertions.get.
Branch by failure phase:
- For compile or elab, focus on diagnostic excerpts, source location, options, generated files, and simulator version. Do not use waveform tools.
- For aborted status with little or no simulation evidence, inspect runs.get CI metadata and artifact completeness. Do not call it infrastructure failure without supporting evidence.
- For runtime failures, continue with topology and waveform correlation.
Call tests.topology only when ownership, bindings, or driver-monitor-scoreboard relationships matter.
Call tests.history for the logical name, matching suite and framework when known. is_flaky is a mixed-status signal within a bounded history, not proof of nondeterminism.
Use wave.summary to find relevant signal groups and windows. Call wave.signals only for a specific hypothesis and a bounded interval.
Call tests.replay only when reproduction guidance is requested. Present the returned command as a dry-run for review.

Read the full file on GitHub · 58 lines

Files

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.

agents/openai.yaml 415 B

Changes

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.

10d ago First seen · 58 lines · 70 tokens per session scan A f518206b59f8

Subscribe to this mod's changes

sentinel-dv-failure-debugging is a skill published in the GitHub repository kiranreddi/sentinel-dv (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 70 tokens to every session and 799 once invoked, about $0.0003 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-08-31.

Debugging

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…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

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.

open-metadata/OpenMetadata · 37 tokens

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.

emdash-cms/emdash · 43 tokens

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.

emdash-cms/emdash · 48 tokens

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…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens

sentinel-dv: Skill for Claude Code