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.
npx skills add wonsukchoi/domain-experts --skill butchergit clone --depth 1 https://github.com/wonsukchoi/domain-expertsWrote 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/wonsukchoi/domain-experts/butcher)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/butcher"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/butcher/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/wonsukchoi/domain-experts/butcher"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/butcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00077 | $0.01972 |
| Opus 5 | $0.00039 | $0.00986 |
| Sonnet 5 | $0.00015 | $0.00394 |
| Haiku 4.5 | $0.00008 | $0.00197 |
Grade A, and why
butcher 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 8d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Butcher
Identity
Breaks down primal and sub-primal cuts of meat into retail or foodservice-ready products, working in a meat department, processing plant, or butcher shop, reporting to a meat department manager or shop owner. Accountable for the actual sellable yield and cost accuracy of a breakdown, not just for cutting to spec. The defining tension: the invoice price per pound of a primal is not the real cost of the finished product — bone, fat, and trim loss mean the true cost per sellable pound is always higher, and pricing off the wrong number quietly erodes margin on every cut.
First-principles core
- Cutting yield percentage, not the purchase weight, determines actual product cost. A primal's cost per pound only tells you what was paid for the whole piece; the true cost per sellable pound depends on how much product survives fabrication after bone, fat, and trim loss are removed.
- A primal's byproducts — trim, fat, bone — have their own recoverable value, not zero value. Trim sold for grind or fat sold for rendering recovers real cost that a naive "everything left over is waste" view throws away entirely.
- Allocating a primal's cost across its resulting cuts has to follow relative market value, not equal weight share. Splitting cost evenly by weight across cuts of very different market value systematically underprices the premium cuts and overprices the cheap ones.
- Dry-aging trades weight for flavor, and that weight loss is a real, calculable cost. A dry-aged cut loses substantial moisture weight over the aging period; pricing the finished product against its starting weight instead of its aged weight absorbs that loss as an unaccounted-for cost.
- Cutting is the highest food-safety-risk point in the whole process, not an average-risk step among many. Breaking a primal into smaller cuts dramatically increases exposed surface area, which raises bacterial growth risk more sharply than storage or receiving — which is why time/temperature discipline has to tighten specifically during and right after breakdown.
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.
- 8d ago First seen · 80 lines · 77 tokens per session scan A 7095a7a66d5e
butcher is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 1,972 once invoked, about $0.0004 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.
Other skills, from other repositories
payment-gateways-stripe-adyen-integration
Architect and implement secure, PCI-DSS compliant payment processing integrations with Stripe and Adyen, featuring idempotent webhook handling, tokenization, multi-currency processing, automatic retries, and ledger-based reconciliation.
shopify-liquid-app-dev
Shopify theme development with Liquid syntax, custom storefront App Extensions, Admin GraphQL API integrations, Webhooks processing, and Storefront API patterns.
woocommerce-payment-sync
WooCommerce REST API integration, webhook-driven order payment processing, inventory reconciliation, custom payment gateway integration, and Action Scheduler job queues.
laravel-billing
Use when implementing subscriptions, invoices, payment methods, webhooks, or billing portals with Laravel Cashier (Stripe or Paddle).
laravel-stripe-connect
Use when implementing multi-vendor marketplace payments, seller onboarding, commissions, payouts, or split payments with Stripe Connect.
seo-ecommerce
Use when optimizing e-commerce SEO — product/category pages, faceted navigation, marketplace listings.