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.
git clone --depth 1 https://github.com/paulnsorensen/easy-cheesenpx agentmods add skills/paulnsorensen/easy-cheese/cureWrote 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/paulnsorensen/easy-cheese/cure)<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.
<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>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
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.
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.00055 | $0.03459 |
| Opus 5 | $0.00028 | $0.01729 |
| Sonnet 5 | $0.00011 | $0.00692 |
| Haiku 4.5 | $0.00006 | $0.00346 |
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.
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/plateto publish when no PR exists.--auto— Use automatic mode from/cook --auto. Skip user selection. Require--stake <floor>./cook --autoalways passesmedium+.--stake <floor>— Set the severity floor for--auto. Acceptblocker,high,medium+, orall. 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
- Load. Read
handoff_context.source_reportfirst when the handoff supplies it. Confirm that the file exists and belongs to the namedsource_skill. Stop withstatus: halt: unreadable source reportwhen this check fails. Read.cheese/age/<slug>.mdwhen the handoff supplies only a slug. Take the typed path only when the handoff also supplies aCurdPlan. Callvalidate_curd_planon 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. - Select. Adopt a locked selection from
/ageor/affinage. Otherwise, apply the recommended composite. Readreferences/selection.mdfor verbs and gate conditions. Expand a user verb with this command:
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.
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.
- 2d ago Changed e3ea6a6ea215
- 4d ago Changed · +143 lines · -23 tokens per session abb453329118
- 6d ago Changed · +2 lines 18e82f0c759a
- 10d ago First seen · 179 lines · 78 tokens per session scan A 96ce2b4318c3
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.
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.
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.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
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…
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…
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.…