cure

cure is a skill for Claude Code from paulnsorensen/easy-cheese. It costs 55 tokens per session (3,459 once invoked), scanned A, original, MIT.

A code-fixing workflow for applying selected problems from a review, report, or failed continuous-integration check. Continuous integration automatically tests project changes.

In plain words
What is it for?
Fixing selected review findings or CI failures, then running the project's tests, lint checks, and build checks before publication.
Why use it?
It turns reported failures into fixes and checks the project afterward, so unresolved issues are less likely to be handed off for release.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 skills/cure/scripts/cure.pyz findings parse-selection --report <path> --selection "<verb>".

Part of the easy-cheese plugin — 18 skills shipped together

not rated 18repo changed 2d ago A scan Socket: passSnyk: passSkillSpector: warn 55 tokens original MIT

Good fit Fixing selected review findings or CI failures, then running the project's tests, lint checks, and build checks before publication.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/paulnsorensen/easy-cheese
agentmods
npx agentmods add skills/paulnsorensen/easy-cheese/cure

Made for: Claude Code.

Or install easy-cheese, the plugin that ships this one along with the rest of its 18 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 cure

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/paulnsorensen/easy-cheese/cure"><img src="https://agentmods.dev/badge/skills/paulnsorensen/easy-cheese/cure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,459 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
  • Socket pass 12 Jun 2026
  • Snyk pass 12 Jun 2026
  • 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 Excessive Agency · line 231
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Agent Snooping · line 266
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00055 $0.03459
Opus 5 $0.00028 $0.01729
Sonnet 5 $0.00011 $0.00692
Haiku 4.5 $0.00006 $0.00346

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

Security

Grade A, and why

cure 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 2d 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.

skills/cure/SKILL.md · 324 lines

How it starts

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

/cure

Use this skill after /age, failed validation, or a request to fix selected review findings.

Inputs

Accept an /age slug, a pasted findings list, a CI failure summary, or a scoped fix instruction.

/cure <slug> reads .cheese/age/<slug>.md.

Adopt a locked selection from /age or /affinage. The canonical format is in references/selection.md#handoff-from-age. Otherwise, apply the recommended composite from references/selection.md. That file also defines the selection gate conditions.

Older Age reports can omit finding fields or confidence. Read references/selection.md § Older report shape before you select from these reports. Do not reject a report because it lacks these fields.

Optional flags:

  • --safe — Restore the selection gate and the final publication gate.
  • --open-pr — Permit /plate to publish when no PR exists.
  • --auto — Use automatic mode from /cook --auto. Skip user selection. Require --stake <floor>. /cook --auto always passes medium+.
  • --stake <floor> — Set the severity floor for --auto. Accept blocker, high, medium+, or all. Ignore this flag without --auto.
  • --hard — Pass the metacognitive gate flag to /plate.

Read references/selection.md for selection rules. Read ## Auto mode for the pass cap and revert behavior. Read ## --hard mode for the metacognitive gate.

Read harness-portability.md for portability rules. Slash commands are host renderings, not the control model.

Flow

  1. Load. Read handoff_context.source_report first when the handoff supplies it. Confirm that the file exists and belongs to the named source_skill. Stop with status: halt: unreadable source report when this check fails. Read .cheese/age/<slug>.md when the handoff supplies only a slug. Take the typed path only when the handoff also supplies a CurdPlan. Call validate_curd_plan on that plan. Stop before dispatch when the plan or its digest is invalid. Do not rebuild a plan from a legacy manifest. Take the report path in every other case.
  2. Select. Adopt a locked selection from /age or /affinage. Otherwise, apply the recommended composite. Read references/selection.md for verbs and gate conditions. Expand a user verb with this command:

Read the full file on GitHub · 324 lines

Files

What ships with it

8 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. 2d ago Changed e3ea6a6ea215
  2. 4d ago Changed · +143 lines · -23 tokens per session abb453329118
  3. 6d ago Changed · +2 lines 18e82f0c759a
  4. 10d ago First seen · 179 lines · 78 tokens per session scan A 96ce2b4318c3

Subscribe to this mod's changes

cure is a skill published in the GitHub repository paulnsorensen/easy-cheese (18 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 3,459 once invoked, about $0.0003 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

systemic-issue-triage

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

Gentleman-Programming/gentle-ai · 57 tokens

issue-root-resolution

Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.

Gentleman-Programming/gentle-ai · 45 tokens

rdd-defect-workflow

Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.

Gentleman-Programming/gentle-ai · 41 tokens

ring:searching-code

Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…

LerianStudio/ring · 74 tokens

ring:test-driven-development

Enforcing the RED-GREEN-REFACTOR loop: write one failing test and watch it fail, write minimal code to pass, then refactor green. Use when starting implementation of a new feature or bugfix, or writing any new production code. Requires pasted failure output as proof of RED; code written before its test must be…

LerianStudio/ring · 89 tokens

vibedrift-drift-check

Use when writing or changing code in an existing repository to keep new code consistent with the repo's own conventions and avoid duplicating code that already exists. Checks a proposed function against the repo's dominant patterns and existing functions BEFORE it lands, turning drift detection into drift prevention.…

VibeDrift/VibeDrift · 74 tokens