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.
npx skills add xuansenpa1/skillrevise --skill lab-unit-harmonizationgit clone --depth 1 https://github.com/xuansenpa1/skillreviseWrote 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.
[](https://agentmods.dev/skills/xuansenpa1/skillrevise/lab-unit-harmonization)<a href="https://agentmods.dev/skills/xuansenpa1/skillrevise/lab-unit-harmonization"><img src="https://agentmods.dev/badge/skills/xuansenpa1/skillrevise/lab-unit-harmonization.svg" alt="Measured on agentmods" height="20"></a>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.00082 | $0.02709 |
| Opus 5 | $0.00041 | $0.01354 |
| Sonnet 5 | $0.00016 | $0.00542 |
| Haiku 4.5 | $0.00008 | $0.00271 |
Grade A, and why
lab-unit-harmonization 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 4d 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.
This is a copy
100% identical to lab-unit-harmonization — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lab Unit Harmonization
Overview
Lab Unit Harmonization provides techniques and references for standardizing clinical laboratory data from multiple sources. Real-world healthcare data often contains measurements in different units, varying decimal and numeric formats, and data entry inconsistencies that must be resolved before analysis.
This skill covers:
- Unit Conversion: Converting between US conventional and SI units
- Format Standardization: Handling scientific notation, decimal formats, whitespace
- Data Quality Assessment: Identifying and quantifying data issues
- CKD-Specific Labs: Complete reference for chronic kidney disease-related lab features
When to Use This Skill
Use this skill when:
- Harmonizing lab values from multiple hospitals or health systems
- Converting between US conventional and SI units (e.g., mg/dL to µmol/L)
- Merging data from EHRs using different default unit conventions
- Integrating international datasets with mixed unit systems
- Standardizing inconsistent numeric formats (scientific notation, decimals)
- Cleaning whitespace, thousand separators, or European decimal formats
- Validating lab values against expected clinical ranges
- Preparing CKD lab panels for eGFR calculations or staging models
- Building ETL pipelines for clinical data warehouses
- Preprocessing lab data for machine learning models
Data Quality Issues Reference
Real-world clinical lab data contains multiple types of quality issues. The following table summarizes common issues and their typical prevalence in multi-source datasets:
| Issue Type | Description | Typical Prevalence | Example |
|---|---|---|---|
| Incomplete Records | Rows with excessive missing values | 1-5% | Patient record with only 3/62 labs measured |
| Mixed Units | Same analyte reported in different units | 20-40% | Creatinine: mg/dL vs µmol/L |
| Scientific Notation | Large/small values in exponential format | 15-30% | 1.5e3 instead of 1500 |
| Thousand Separators | Commas in large numbers | 10-25% | 1,234.5 vs 1234.5 |
| European Decimals | Comma as decimal separator | 10-20% | 12,5 instead of 12.5 |
| Whitespace Issues | Leading/trailing spaces, tabs | 15-25% | 45.2 vs 45.2 |
| Missing Values | Empty, NULL, or sentinel values | Variable | NaN, -999, blank |
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.
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.
- 4d ago First seen · 260 lines · 82 tokens per session scan A 60eea92e906b
lab-unit-harmonization is a skill published in the GitHub repository xuansenpa1/skillrevise (55 stars, last pushed 2d ago), licensed MIT. It adds 82 tokens to every session and 2,709 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to lab-unit-harmonization, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…