score-quality

score-quality is a skill for Claude Code, Codex from OpenHands/extensions. It costs 23 tokens per session (328 once invoked), scanned A, original, MIT.

A review tool for judging how well code was moved from one system to another. It compares mapped source and target files for missing functionality and changed behaviour, then assigns coverage and correctness scores from 1 to 5.

In plain words
What is it for?
Use it after a migration to check business logic, data fields, control flow, error handling, calculations, and edge cases in the target code.
Why use it?
It makes migration gaps easier to find than relying on a general code review. It records specific reasons for each score and can update an existing score file.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it after a migration to check business logic, data fields, control flow, error handling, calculations, and edge cases in the target code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/openhands/extensions/score-quality
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 OpenHands/extensions --skill score-quality
Clone the repo
git clone --depth 1 https://github.com/OpenHands/extensions

Made for: Claude Code, Codex.

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.

agentmods badge for score-quality

README.md
[![agentmods](https://agentmods.dev/badge/skills/openhands/extensions/score-quality/github.svg)](https://agentmods.dev/skills/openhands/extensions/score-quality)
Your own site
<a href="https://agentmods.dev/skills/openhands/extensions/score-quality"><img src="https://agentmods.dev/badge/skills/openhands/extensions/score-quality/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.

agentmods 80×15 button for score-quality

Your own site · 80×15
<a href="https://agentmods.dev/skills/openhands/extensions/score-quality"><img src="https://agentmods.dev/badge/skills/openhands/extensions/score-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 328 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00328
Opus 5.5 $0.00009 $0.00131
Sonnet 5.5 $0.00005 $0.00066
Haiku 4.5 $0.00002 $0.00033

Measured 1mo ago against content hash c0a0955e32ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

score-quality 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 1mo 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.

plugins/migration-scoring/skills/score-quality/SKILL.md · 55 lines

What it actually says

Evaluate migration quality by scoring coverage and correctness for each source-target file pair.

Prerequisite: A migration mapping file must exist (see migration-mapping skill).

See references/scoring-criteria.md for the 1-5 scoring scales.

Output Format

Save scores as a JSON file:

{
  "source_file_1.cbl": {
    "coverage": 4,
    "correctness": 5,
    "justification": "All calculation logic migrated. Tax rounding matches COBOL behavior."
  }
}

Evaluation Process

For each source file and its mapped target files:

  1. Identify key functionality in the source

    • Business logic, data operations, control flow, error handling
  2. Check coverage in the target

    • Is each function/paragraph represented?
    • Are all data fields and code paths covered?
  3. Verify correctness

    • Do calculations produce the same results?
    • Are edge cases handled the same way?
  4. Document justification

    • Specific functionality present/missing
    • Known discrepancies

Incremental Scoring

If a score file already exists, update it with new scores rather than replacing it entirely.

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.

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.

  1. 1mo ago First seen · 55 lines · 23 tokens per session scan A c0a0955e32ef

Subscribe to this mod's changes

score-quality is a skill published in the GitHub repository OpenHands/extensions (167 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 328 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens