health-check

health-check is a skill for Claude Code from ludo-technologies/pyscn. It costs 49 tokens per session (419 once invoked), scanned A, original, MIT.

A tool for measuring the overall quality of Python code with pyscn, which reports a score from 0 to 100, a letter grade, and several code-quality categories.

In plain words
What is it for?
Use it when assessing Python code health, reviewing complexity, duplication, dead code, dependencies, or architecture. It can produce machine-readable details and save fuller reports for inspection.
Why use it?
It gives a quick overview of technical debt and shows which areas or files most need attention. It can also compare code quality before and after a refactor.

Skill for Claude Code

Written for Claude Code: a Claude Code plugin manifest.

Part of the pyscn-mcp plugin — 4 skills shipped together

Good fit Use it when assessing Python code health, reviewing complexity, duplication, dead code, dependencies, or architecture. It can produce machine-readable details and save fuller reports for inspection.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ludo-technologies/pyscn/health-check
About the project

pyscn is a Python code-quality analyzer that examines dead code, duplication, complexity, hotspots, architecture, dependencies, and class design, then reports which areas need attention. It is used to maintain and refactor codebases, including AI-generated code, and provides agent skills for health checks, architecture reviews, refactoring, and CI reports.

ludo-technologies/pyscn · 1,099 stars · on GitHub · docs.codescan.dev

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 ludo-technologies/pyscn --skill health-check
Clone the repo
git clone --depth 1 https://github.com/ludo-technologies/pyscn

Made for: Claude Code.

Or install pyscn-mcp, the plugin that ships this one along with the rest of its 4 skills.

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 health-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/ludo-technologies/pyscn/health-check/github.svg)](https://agentmods.dev/skills/ludo-technologies/pyscn/health-check)
Your own site
<a href="https://agentmods.dev/skills/ludo-technologies/pyscn/health-check"><img src="https://agentmods.dev/badge/skills/ludo-technologies/pyscn/health-check/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 health-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/ludo-technologies/pyscn/health-check"><img src="https://agentmods.dev/badge/skills/ludo-technologies/pyscn/health-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 419 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 warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 11
    uvx/uv tool run commands without ==version create a rug-pull risk.
    Fix: Pin the version: uvx package-name==1.2.3
  • medium MCP Rug Pull · line 20
    uvx/uv tool run commands without ==version create a rug-pull risk.
    Fix: Pin the version: uvx package-name==1.2.3
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.00049 $0.00419
Opus 5.5 $0.00020 $0.00168
Sonnet 5.5 $0.00010 $0.00084
Haiku 4.5 $0.00005 $0.00042

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

Security

Grade A, and why

health-check 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 2mo 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.

.claude-plugin/pyscn-mcp/skills/health-check/SKILL.md · 37 lines

What it actually says

Python Code Health Check with pyscn

Run the pyscn CLI to give a quick, quantified picture of code quality. No install needed:

uvx pyscn@latest analyze <path>

The summary output includes a health score (0-100), a letter grade (A-F), and per-category metrics.

Commands

User Request Command
"How healthy is this code?" uvx pyscn@latest analyze <path>
"Give me a quality overview" Same command; walk through the category breakdown
"Did my refactoring improve quality?" Run before and after, compare scores

For machine-readable detail add --json. Report files are NOT written to stdout. They go to .pyscn/reports/ under the current working directory and the path is printed on completion; read that file.

Interpreting Results

  • Score 0-100 with letter grade; category breakdowns cover complexity, dead code, duplication, coupling (CBO), cohesion (LCOM), dependencies, and architecture.
  • Lead with the grade and the weakest categories, then name the top offenders (files/functions) driving them.
  • For deeper follow-up, hand off to the focused skills: refactoring targets → refactoring, module structure → architecture-review.

Always explain the score in plain terms and suggest the highest-impact next step.

MCP Alternative

If the pyscn-mcp MCP server is connected, you can use its tools instead of the CLI: get_health_score (score + grade) or analyze_code (output_mode: "summary" gives the health score plus high-level metrics per category). Results are returned inline with no report files.

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. 2mo ago First seen · 37 lines · 49 tokens per session scan A a55a96cd62de

Subscribe to this mod's changes

health-check is a skill published in the GitHub repository ludo-technologies/pyscn (1,099 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 419 once invoked, about $0.0002 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.