What is quality-dashboard?

A project health report that combines results from security scans, test coverage, and lint checks into one view and a score from 0 to 100.

Aggregating quality metrics, checking quality gates, summarising project health, and preparing status reports after the related checks have run.

It removes the need to inspect several quality reports separately when checking whether code is ready for review or deployment.

How mehdic/bazinga configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to mehdic/bazinga. 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/mehdic/bazinga/main/.claude/skills/quality-dashboard/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/mehdic/bazinga

Made for: Claude Code.

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/mehdic/bazinga/quality-dashboard.svg)](https://agentmods.dev/skills/mehdic/bazinga/quality-dashboard)

Your own site

<a href="https://agentmods.dev/skills/mehdic/bazinga/quality-dashboard"><img src="https://agentmods.dev/badge/skills/mehdic/bazinga/quality-dashboard.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,337 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.00012	$0.01337
Opus 5	$0.00006	$0.00668
Sonnet 5	$0.00002	$0.00267
Haiku 4.5	$0.00001	$0.00134

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

Security

Grade A, and why

quality-dashboard 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 7d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/dashboard.ps1, scripts/dashboard.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/quality-dashboard/SKILL.md · 214 lines

How it starts

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

Quality Dashboard Skill

You are the quality-dashboard skill. When invoked, you aggregate metrics from all quality tools to provide a comprehensive, unified view of project health with a single health score (0-100).

When to Invoke This Skill

Invoke this skill when:

After running security-scan, test-coverage, and lint-check
Before final code review or deployment
PM needs overall project health status
Generating status reports for stakeholders
Checking if quality gates pass

Do NOT invoke when:

Quality tools haven't run yet (no metrics available)
Emergency hotfixes (skip quality dashboard)
Work-in-progress code not ready for review

Your Task

When invoked:

Execute the quality dashboard aggregation script
Read the generated dashboard report
Return a summary to the calling agent

Step 1: Execute Quality Dashboard Script

Use the Bash tool to run the pre-built dashboard script.

On Unix/macOS:

bash .claude/skills/quality-dashboard/scripts/dashboard.sh

On Windows (PowerShell):

pwsh .claude/skills/quality-dashboard/scripts/dashboard.ps1

Cross-platform detection: Check if running on Windows ($env:OS contains "Windows" or uname doesn't exist) and run the appropriate script.

This script will:

Read bazinga/security_scan.json
Read bazinga/coverage_report.json
Read bazinga/lint_results.json
Read bazinga/project_metrics.json
Calculate component scores (0-100 for each)
Compute overall health score (weighted average)
Detect trends by comparing to previous run
Identify anomalies
Generate bazinga/artifacts/{SESSION_ID}/skills/quality_dashboard.json

Step 2: Read Generated Report

Use the Read tool to read:

bazinga/artifacts/{SESSION_ID}/skills/quality_dashboard.json

Extract key information:

overall_health_score - Single score 0-100
health_level - excellent/good/fair/poor/critical
metrics.security.score - Security component score
metrics.coverage.score - Coverage component score
metrics.lint.score - Lint component score
metrics.velocity.score - Velocity component score
quality_gates_status - passed/failed for each gate
anomalies - Detected issues
recommendations - Action items

Read the full file on GitHub · 214 lines

Files

What ships with it

2 files 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.

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.

7d ago First seen · 214 lines · 12 tokens per session scan A 5ac08d3b9c03

Subscribe to this mod's changes

quality-dashboard is a skill published in the GitHub repository mehdic/bazinga (21 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 1,337 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-08-30.

Analytics and metrics

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

bazinga: Skill for Claude Code