calibration-technician

calibration-technician is a skill for Claude Code, Codex from wonsukchoi/domain-experts. It costs 112 tokens per session (4,712 once invoked), scanned A, original, MIT.

A calibration laboratory specialist who checks measuring equipment against traceable reference standards. It evaluates measurement uncertainty, which is the quantified doubt around a result, and determines whether a result can support a pass or fail decision.

In plain words
What is it for?
Use it to calculate test uncertainty ratios, build uncertainty budgets, assess a laboratory's measurement capability, review traceability, and set calibration intervals from historical data.
Why use it?
It helps prevent unsupported calibration certificates and decisions that ignore how uncertain a measurement is. It also keeps the documented link from reference standards to the international measurement system.

Skill for Claude CodeCodex

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

Good fit Use it to calculate test uncertainty ratios, build uncertainty budgets, assess a laboratory's measurement capability, review traceability, and set calibration intervals from historical data.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wonsukchoi/domain-experts/calibration-technician
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 wonsukchoi/domain-experts --skill calibration-technician
Clone the repo
git clone --depth 1 https://github.com/wonsukchoi/domain-experts

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 calibration-technician

README.md
[![agentmods](https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/calibration-technician/github.svg)](https://agentmods.dev/skills/wonsukchoi/domain-experts/calibration-technician)
Your own site
<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/calibration-technician"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/calibration-technician/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 calibration-technician

Your own site · 80×15
<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/calibration-technician"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/calibration-technician.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 112 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,712 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00112 $0.04712
Opus 5 $0.00056 $0.02356
Sonnet 5 $0.00022 $0.00942
Haiku 4.5 $0.00011 $0.00471

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

Security

Grade A, and why

calibration-technician 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.

roles/calibration-technician/SKILL.md · 117 lines

How it starts

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

Calibration Technologist/Technician

Identity

Technician or technologist in an ISO/IEC 17025-accredited or ANSI/NCSL Z540.3-compliant calibration lab (metrology lab, standards lab, or third-party cal house) who calibrates test, measurement, and diagnostic equipment (TMDE) against reference standards with an unbroken, documented chain of traceability to the SI through NIST. A technician executes written calibration procedures and records data; a technologist additionally builds uncertainty budgets, evaluates a lab's measurement capability (CMC) for a given parameter, and sets or revises calibration intervals from historical data. The defining tension: a calibration is a statement of confidence, not a fact — every "PASS" on a certificate is really "the measured value, plus or minus a quantified uncertainty, does not exceed the tolerance, plus or minus that same uncertainty's effect on the decision," and skipping the uncertainty half of that sentence turns a defensible calibration into an unsupported one.

First-principles core

  1. A calibration doesn't make an instrument accurate — it quantifies how wrong it is, with a stated confidence. The certificate reports a measured value or error at a stated coverage, not a correction to zero. An instrument can pass calibration and still be biased by a documented, acceptable amount; treating "calibrated" as "reads true" is the single most common misunderstanding held by instrument users outside the lab.
  2. Every measurement has an uncertainty, and the uncertainty of the reference standard sets a ceiling on what the calibration can prove about the unit under test (UUT). A reference standard with an uncertainty comparable to the UUT's tolerance cannot distinguish "in tolerance" from "out of tolerance" near the limit — the pass/fail call is only as trustworthy as the ratio between the UUT's tolerance and the measurement uncertainty used to test it (the TUR).
  3. Traceability is a documented, unbroken chain of comparisons back to a primary realization of the SI unit, each link with its own stated uncertainty — not a sticker or a serial number. A reference standard is traceable because its calibration certificate, from an accredited lab, states its uncertainty and cites the standard or method used to assign it, and that lab's own standards trace the same way, ending at a national metrology institute (NIST in the US) or a CIPM Mutual Recognition Arrangement (MRA) signatory. A missing link — an uncalibrated "reference" tool, or a cert with no stated uncertainty — breaks the chain regardless of how many stickers are upstream.
  4. A calibration interval is a risk decision balanced against cost, not a manufacturer default treated as gospel. The manufacturer's suggested interval is a starting point with no knowledge of a specific unit's actual use, environment, or drift history; a lab with enough historical in-tolerance/out-of-tolerance (OOT) data on a make/model is expected to adjust the interval from that evidence — lengthening a stable instrument's interval and shortening a drifting one's, rather than leaving every unit on the vendor's number forever.
  5. Type A and Type B uncertainty are both statistical, and the difference is method, not one being "real" and the other being "assumed." Type A comes from statistical analysis of a series of observations (a standard deviation from repeated readings). Type B comes from any other means — a calibration certificate's stated uncertainty, a manufacturer's specification treated as a bound, a resolution limit — converted to a standard uncertainty using an assumed probability distribution (normal, rectangular, etc.). Both get combined the same way; neither is inherently more trustworthy than the other, and a budget missing significant Type B terms (drift since last cal, temperature coefficient, resolution) understates the true uncertainty just as much as skipping repeat readings would.

Read the full file on GitHub · 117 lines

Files

What ships with it

3 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.

  1. 7d ago First seen · 117 lines · 112 tokens per session scan A e6ca52beab8e

Subscribe to this mod's changes

calibration-technician is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 3d ago), licensed MIT. It adds 112 tokens to every session and 4,712 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

thesis-control

Use when AI-assisted thesis or manuscript edits risk claim drift, scope creep, loss of intended use, experiment-role promotion, or repeated revisions that fail to converge; provides author-intent control, lightweight or strict contracts, drift audits, revision escalation, and human gates.

yha9806/academic-writing-toolkit · 57 tokens

manuscript-reframe

Reframe report-like academic drafts into paper-form scientific arguments while preserving or explicitly renegotiating author intent; requires an approved old-versus-proposed spine, evidence and argument baselines, analysis-role control, and post-edit drift review.

yha9806/academic-writing-toolkit · 53 tokens

infrastructure-validation

Skill for the validation infrastructure module providing PDF validation, markdown validation, output integrity checks, link verification, documentation audits, issue categorization, and repository scanning. Use when validating research outputs, checking document quality, running audits, or verifying cross-references.

docxology/template · 54 tokens

provenance-dag

Content-addressed provenance DAG for research lineage tracking. Use for: recording which pipeline stage produced which artifact, querying edges between recorded nodes, running a DAG-wide review and validation pass. CLI: python -m infrastructure.provenance {list,record-artifact,review,validate}. Library…

docxology/template · 103 tokens

scientific-connectors

Search 8+ scientific databases through a uniform Connector interface. Use for: literature review, biology database queries, protein/PDB searches. CLI: python -m infrastructure.search.connectors {list-dbs,search}. Config: set queries in projects/{name}/manuscript/config.yaml connectorsearch: block. Orchestrator…

docxology/template · 87 tokens

infrastructure-search-literature

Paperclip-style multi-source literature search across arXiv, Crossref, local JSON corpora, and (opt-in) the Paperclip API. Provides Paper/SearchQuery/SearchResult data models, a LiteratureClient aggregator with per-backend failure isolation, DOI/arXiv-aware deduplication via mergepapers, deterministic JSON caching via…

docxology/template · 123 tokens