medharness: Skill for Claude Code

.claude/skills/openspec-apply-change/SKILL.md

openspec-apply-change is a skill for Claude Code from charliehzm/medharness. It costs 179 tokens per session (619 once invoked), scanned A, original, Apache-2.0.

A controlled implementation step for one task in an OpenSpec change. OpenSpec is a way to organize a proposed code change into specifications and task documents.

In plain words
What is it for?
Use it to read one task, implement it across no more than two files, run a quick sanity check, and mark that task complete.
Why use it?
It keeps each code change small and tied to one documented task. It also checks data handling and prevents unrelated cleanup or changes from being bundled in.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is charliehzm/medharness's own configuration. It tells Claude Code how to work on medharness itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything medharness configures →

Reuse

Borrowing it

Nothing to install: this file belongs to charliehzm/medharness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/charliehzm/medharness/main/.claude/skills/openspec-apply-change/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/charliehzm/medharness

Made for: Claude Code.

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 openspec-apply-change

README.md
[![agentmods](https://agentmods.dev/badge/skills/charliehzm/medharness/openspec-apply-change/github.svg)](https://agentmods.dev/skills/charliehzm/medharness/openspec-apply-change)
Your own site
<a href="https://agentmods.dev/skills/charliehzm/medharness/openspec-apply-change"><img src="https://agentmods.dev/badge/skills/charliehzm/medharness/openspec-apply-change/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 openspec-apply-change

Your own site · 80×15
<a href="https://agentmods.dev/skills/charliehzm/medharness/openspec-apply-change"><img src="https://agentmods.dev/badge/skills/charliehzm/medharness/openspec-apply-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 179 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 619 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.00179 $0.00619
Opus 5 $0.00089 $0.00309
Sonnet 5 $0.00036 $0.00124
Haiku 4.5 $0.00018 $0.00062

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

Security

Grade A, and why

openspec-apply-change 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 11d 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/skills/openspec-apply-change/SKILL.md · 55 lines

What it actually says

OpenSpec Apply Change

The implementation step. One task per invocation. Stay in scope.

Discipline

  • Read the task document; do exactly what it says.
  • Do not bundle unrelated cleanup.
  • Do not refactor adjacent code.
  • Do not add comments unless WHY is non-obvious.
  • If the task is wrong/incomplete, stop and route to prd-implementation-precheck instead.

Workflow

  1. Open the task document.
  2. Read the linked spec(s) for acceptance criteria.
  3. If any data-handling code involves L3/L4 → call phi-desensitize first; never paste raw values.
  4. Plan diff mentally; if > 2 files needed, re-decompose (call task-decomposition).
  5. Apply changes.
  6. Run quick local sanity (type-check, single test).
  7. Flip the task document checkbox to [x].
  8. Do NOT mark the OpenSpec change as done — that's Step 7 Verify.

Common failure modes

  1. Scope creep — "while I'm here, let me also fix..." . Mitigation: discipline; flag adjacent issues to spawn_task-style follow-up, not inline.
  2. Bigger diff than spec — finish the task with 4 files. Mitigation: pause at file 2; re-decompose.
  3. PHI in prompt — pasted real schema row including patient_id. Mitigation: hook + skill enforcement.
  4. Comments that re-describe code — adds noise. Mitigation: comments only where WHY is non-obvious.
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. 11d ago First seen · 55 lines · 179 tokens per session scan A 0ade70ae3a4c

Subscribe to this mod's changes

openspec-apply-change is a skill published in the GitHub repository charliehzm/medharness (86 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 179 tokens to every session and 619 once invoked, about $0.0009 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-08-30.

Related

Other skills, from other repositories

hipaa-review

Performs a HIPAA Security Rule compliance review against all Administrative, Physical, and Technical Safeguards defined in 45 CFR Part 164, Subpart C. Auto-invoked when discussing healthcare data security, ePHI protection, HIPAA audit readiness, or business associate compliance. Evaluates required and addressable…

UnitOneAI/SecuritySkills · 86 tokens

HIPAA Compliance Testing

Testing HIPAA compliance for healthcare applications including PHI handling, audit logging, access controls, and data encryption verification.

PramodDutta/qaskills · 28 tokens

Healthcare Compliance

HIPAA compliance, healthcare regulations, privacy and security standards for medical organizations and providers.

jmsktm/claude-settings · 19 tokens

compliance

Use when scoping which regulatory frameworks bind a business — SOC 2, ISO 27001, HIPAA, PCI DSS, EU AI Act, DORA, NIS2 — building a control register with owners and evidence, or standing up the cadence that keeps it audit-ready. NOT drafting privacy-policy/ROPA/DPA or ToS text (that is gdpr-privacy, terms-conditions)…

ericrisco/rsc-harness · 96 tokens

healthcare-expert

Expert-level healthcare systems, medical informatics, HIPAA compliance, and health data standards. Use when the user mentions medical, HIPAA, HL7, FHIR, or EHR, or when the task involves Healthcare IT, Standards and Protocols, Regulatory Compliance, or Security and Compliance.

personamanagmentlayer/pcl · 64 tokens

performing-soc2-type2-audit-preparation

Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security…

adriannoes/awesome-agentic-ai · 112 tokens