What is quality-metrics?

A reference for measuring test coverage, code quality, defects, and QA performance. Coverage metrics show which lines, branches, functions, and statements have been exercised by tests.

Use it to define coverage targets, track coverage trends, measure code complexity and defects, and set quality checks in continuous integration.

It helps teams see where testing is incomplete, where code may be hard to maintain, and whether quality is improving over time.

quality-metrics — Skill for Claude Code by MonumentalSystems

Install

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.

Any agent

npx skills add MonumentalSystems/Atlas-Agent-Teams --skill quality-metrics

Clone the repo

git clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-Teams

Made for: Claude Code.

Or install qa-testing, the plugin that ships this one along with the rest of its 4 skills, 1 command, 5 agents.

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/monumentalsystems/atlas-agent-teams/quality-metrics/github.svg)](https://agentmods.dev/skills/monumentalsystems/atlas-agent-teams/quality-metrics)

Your own site

<a href="https://agentmods.dev/skills/monumentalsystems/atlas-agent-teams/quality-metrics"><img src="https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/quality-metrics/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/monumentalsystems/atlas-agent-teams/quality-metrics"><img src="https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/quality-metrics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,970 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00017	$0.01970
Opus 5	$0.00009	$0.00985
Sonnet 5	$0.00003	$0.00394
Haiku 4.5	$0.00002	$0.00197

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

Security

Grade A, and why

quality-metrics 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.

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.

teams/qa-testing/skills/quality-metrics/SKILL.md · 293 lines

How it starts

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

Quality Metrics

Test Coverage Metrics

Code Coverage Types

Line Coverage: Percentage of executable lines executed
Branch Coverage: Percentage of conditional branches taken
Function Coverage: Percentage of functions/methods called
Statement Coverage: Percentage of statements executed
Condition Coverage: Percentage of boolean sub-conditions evaluated

Coverage Targets

Critical Business Logic: 90-100%
Core Application Code: 80-90%
Utility/Helper Code: 70-80%
Configuration/Setup Code: 50-70%

Coverage Tools

JavaScript: Istanbul, nyc, Jest coverage
Python: pytest-cov, coverage.py
Java: JaCoCo, Cobertura
.NET: dotCover, Coverlet
Go: go test -cover

Coverage Best Practices

Focus on meaningful coverage, not just percentage
Prioritize coverage of critical paths
Track coverage trends over time
Set coverage gates in CI/CD
Review uncovered code regularly

Code Quality Metrics

Cyclomatic Complexity

Measures code complexity based on control flow
Higher complexity = harder to test and maintain
Target: < 10 per function/method

Complexity Levels:
1-10: Simple, low risk
11-20: Moderate complexity, medium risk
21-50: High complexity, high risk
50+: Very high complexity, very high risk

Maintainability Index

Composite metric combining complexity, volume, and structure
Scale: 0-100 (higher is better)
Target: > 70

Maintainability Levels:
85-100: Highly maintainable
70-84: Moderately maintainable
50-69: Difficult to maintain
0-49: Very difficult to maintain

Code Duplication

Percentage of duplicated code
Target: < 5%
High duplication indicates need for refactoring

Code Smells

Long Methods: Methods > 50 lines
Large Classes: Classes > 500 lines
Deep Nesting: Nesting > 4 levels
Long Parameter Lists: > 4 parameters
Feature Envy: Methods using other objects more than their own

Technical Debt Ratio

Technical Debt Ratio = Cost to Fix Issues / Cost to Develop New Features
Target: < 5%

Read the full file on GitHub · 293 lines

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 · 293 lines · 17 tokens per session scan A c4045d123001

Subscribe to this mod's changes

quality-metrics is a skill published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 1,970 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.

Analytics and metrics Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

quality-metrics