What is sentinel-dv-coverage-closure?

A tool for finding and planning fixes for missing hardware-test coverage. Coverage measures which behaviors, code paths, signal changes, state-machine paths, and assertions have actually been tested.

Use it to inspect coverage gaps and trends, investigate stalled or falling coverage, review vacuous assertions, and propose protocol-aware constraints for later testing. A new indexed run is still needed to prove closure.

It turns coverage data into a prioritized plan, helping teams focus on important untested cases instead of chasing a percentage alone. Empty or missing data is treated as unavailable evidence, not as zero coverage.

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-coverage-closure/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-coverage-closure/github.svg)](https://agentmods.dev/skills/kiranreddi/sentinel-dv/sentinel-dv-coverage-closure)

Your own site

<a href="https://agentmods.dev/skills/kiranreddi/sentinel-dv/sentinel-dv-coverage-closure"><img src="https://agentmods.dev/badge/skills/kiranreddi/sentinel-dv/sentinel-dv-coverage-closure/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-coverage-closure"><img src="https://agentmods.dev/badge/skills/kiranreddi/sentinel-dv/sentinel-dv-coverage-closure.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 780 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.00780
Opus 5	$0.00035	$0.00390
Sonnet 5	$0.00014	$0.00156
Haiku 4.5	$0.00007	$0.00078

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

Security

Grade A, and why

sentinel-dv-coverage-closure 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 11d 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-coverage-closure/SKILL.md · 56 lines

How it starts

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

Sentinel DV Coverage Closure

Convert indexed coverage into a risk-based closure plan. Generated constraints are candidates for review; only a later indexed run can demonstrate closure.

Inputs

Accept a run, suite, coverage kind, protocol, target percentage, baseline, and known exclusions. Resolve omitted run IDs from indexed coverage, but do not invent goals or exclusions.

Preflight

Confirm the Sentinel DV tools are available with coverage.list using page=1.
If unavailable, report that the Sentinel DV MCP server must be configured and coverage artifacts indexed.
Treat absent coverage kinds or empty summaries as missing data, not 0% coverage.

Workflow

Establish the target run or suite, coverage kind, protocol, baseline run, goal, and known exclusions.
If the run is unknown, page through coverage.list to discover indexed records. Call coverage.summary for the selected run_id and optional kind.
Call coverage.trend with the exact supported inputs: suite, kind, and limit. It reports per-run averages, not per-bin age or an arbitrary time window.
Call coverage.gaps with run_id whenever closing a specific run. Narrow with suite, kind, priority, and threshold_pct as needed. Page through all intended results.
For assertion goals, page through assertions.vacuity and assertions.sva_status in the same run scope. Separate unexercised antecedents, failing properties, disabled properties, and missing status data.
If a baseline exists, call runs.diff and use coverage_deltas to distinguish improved, regressed, added, and removed metrics.
Select a valid, reachable functional gap. Call coverage.advisor with its exact run_id, metric_name, optional kind, and protocol context. Treat constraint_sv and sequence_hint as templates requiring source and testbench review.
Use tests.topology and tests.history only after identifying a candidate owner or existing test. Do not infer ownership from coverage scope alone.
Call runs.submit only when a dry-run follow-up command is requested.

Read the full file on GitHub · 56 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 433 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.

11d ago First seen · 56 lines · 70 tokens per session scan A 797b8004c838

Subscribe to this mod's changes

sentinel-dv-coverage-closure 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 780 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.

Hardware and IoT Testing

jetson-video-pipeline

Use when executing and verifying Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or acceptance workflows with exact artifact handoffs.

NVIDIA/skills · 45 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

holohub-app-lifecycle

Use for non-failing HoloHub app work with ./holohub: scaffold, build, run, test, visual evidence, lint, and flow benchmarking.

NVIDIA/skills · 40 tokens

code-plan

Turn a task description and repository into a structured implementation plan (files to create, files to modify, tests to add, risks).

initializ/forge · 29 tokens

ros2-robotics

Best practices for ROS 2 robotics development, covering package structure, nodes, topics/services/actions, launch files, QoS, tf2 transforms, and testing. Use when creating ROS 2 packages, writing nodes in rclpy or rclcpp, defining custom messages/services/actions, writing launch files, configuring QoS profiles…

Mindrally/skills · 87 tokens

SmartHome Video Anomaly Benchmark

VLM evaluation suite for video anomaly detection in smart home camera footage.

SharpAI/DeepCamera · 20 tokens

sentinel-dv: Skill for Claude Code