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/pasteurizeWrote 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/pasteurize)<a href="https://agentmods.dev/skills/paulnsorensen/easy-cheese/pasteurize"><img src="https://agentmods.dev/badge/skills/paulnsorensen/easy-cheese/pasteurize.svg" alt="Measured on agentmods" height="20"></a>- Socket warn
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Data Exfiltration · line 185 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00127 | $0.03700 |
| Opus 5 | $0.00063 | $0.01850 |
| Sonnet 5 | $0.00025 | $0.00740 |
| Haiku 4.5 | $0.00013 | $0.00370 |
Grade A, and why
pasteurize 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 yesterday.
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 — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pasteurize
Use this process for hard bugs.
Discipline
Iron Law: Build a reliable feedback loop before you form one hypothesis.
Stop at each red flag:
- You name a cause before the loop reproduces the failure.
- You accept an unrelated failure as the reproduction.
- You add a test at a mocked seam because the real seam is difficult.
- You make a fourth fix attempt on the same hypothesis list.
- You report a clean worktree without the session-tag sweep.
| Rationalization | Answer |
|---|---|
| "The cause is obvious." | Build the loop. An obvious cause takes one run to confirm. |
| "The loop is too slow to write." | A slow loop still beats a wrong fix. |
| "Any failure proves the bug." | Match the expected exit code or output. |
| "The mocked seam is close enough." | Record the missing seam and route to Mold. |
| "One more attempt will work." | Write a new hypothesis list first. |
Follow code-intelligence-routing.md when you explore code.
Resolve the specification store with artifact-path specs.
Read the notes about the failed seam from the resolved directory.
Read harness-portability.md for portable tool use.
Use bundled or repository helpers before ${CLAUDE_SKILL_DIR}.
Treat ${CLAUDE_SKILL_DIR} as an optional host fallback.
Use the handoff blocks as the portable contract.
Remember that slash commands are host renderings, not the control model.
Inputs
<input> is the reported symptom.
Accept a bug report, a stack trace, failing test output, or an artifact path.
Accept an investigation request from Affinage, Cheese, or Cook.
An investigation request uses these fields:
| Field | Type | Required | Meaning |
|---|---|---|---|
source |
string | yes | The requesting skill, such as affinage. |
source_ref |
string | no | The pull request comment or finding identifier. |
symptom |
string | yes | The reported failure in one sentence. |
expect_exit |
integer | no | The exit code that shows the failure. |
expect_output |
string | no | A regular expression for the failure output. |
mode |
string | no | investigate or fix. The default is fix. |
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.
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.
- yesterday Changed · +178 lines · -42 tokens per session a4279f6daf9b
- 3d ago Changed bb55db5f1504
- 7d ago First seen · 243 lines · 169 tokens per session scan A 336112b2f0ac
pasteurize is a skill published in the GitHub repository paulnsorensen/easy-cheese (18 stars, last pushed today), licensed MIT. It adds 127 tokens to every session and 3,700 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-08-30.
Other skills, from other repositories
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…
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.
gentle-ai-bench
Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.