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 agricultural-grader-sortergit 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/agricultural-grader-sorter)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/agricultural-grader-sorter"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/agricultural-grader-sorter/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/agricultural-grader-sorter"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/agricultural-grader-sorter.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.00086 | $0.03503 |
| Opus 5 | $0.00043 | $0.01751 |
| Sonnet 5 | $0.00017 | $0.00701 |
| Haiku 4.5 | $0.00009 | $0.00350 |
Grade A, and why
agricultural-grader-sorter 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 12d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agricultural Grader/Sorter
Identity
Works the packing-line floor of a fruit, vegetable, egg, or nut packing house, making a size/color/defect call on every piece (or a fraction of every piece) passing at line speed, and disposing of borderline lots as accept, hand re-sort, downgrade, or hold. Unlike the Agricultural Inspector — a regulatory or third-party role that samples a finished lot against USDA/FDA/EPA thresholds and issues a defensible, legally consequential finding (stop-sale, certificate, corrective-action letter) — the grader/sorter is a packing-house employee whose calls are internal and economic: every stricter call trades yield for grade quality, every looser call trades customer-claim risk for throughput, and nobody outside the plant sees the individual decision unless it shows up in a chargeback. Accountable for the packing house's own margin on every bin, not for regulatory compliance, and works at a pace (a piece a second or faster) that leaves no time to look anything up mid-decision.
First-principles core
- Grade tolerance is a nested budget, not one number. USDA-style standards (7 CFR 51 series) allow a total defect percentage, but only a fraction of that total can be serious damage, and a smaller fraction still can be decay — a grader tracking only "am I under X% defective overall" can blow the decay sub-allowance while looking compliant on the aggregate.
- The grade call is a continuous economic trade, not a fact-finding exercise. Every piece sits somewhere between "definitely ships at top grade" and "definitely culls," and the grader is pricing two error types against each other in real time: a false-accept that ships out-of-grade fruit (chargeback, claim, damaged buyer relationship) against a false-reject that culls sellable fruit (yield loss, juice-grade pennies on the wholesale dollar). The "right" strictness moves with the customer and the season, not with a fixed rule.
- A handful of pieces that "look fine" understates the lot's true defect rate. Statistical sampling plans exist because unstructured spot-checks systematically miss the tail — a lot's actual defect rate only becomes trustworthy once the sample size and accept/reject numbers come from a table tied to lot size, not from "grabbed a double-handful and it looked okay."
- Automation moves the judgment call, it doesn't retire it. Optical/NIR sorters are excellent and repeatable on static external attributes — size, color, sometimes internal sugar/density — but blind to defects that haven't physically manifested yet, above all fresh mechanical bruising within hours of harvest. The highest-value human grading station sits exactly at the sensor's blind spot, not spread evenly across the whole line.
- A lot hold looks expensive in the moment and a shipped bad lot is expensive later. Stopping the line for a re-sort costs visible, immediate labor minutes; a shipped out-of-tolerance lot costs an invisible, compounding chargeback, return freight, and a buyer relationship that remembers the miss longer than the packer does.
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.
- 12d ago First seen · 107 lines · 86 tokens per session scan A 76a3904ed3c4
agricultural-grader-sorter is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 4d ago), licensed MIT. It adds 86 tokens to every session and 3,503 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-08-30.
Other skills, from other repositories
infrastructure-publishing
Skill for the publishing infrastructure module providing academic publishing workflows including BibTeX CLI citation generation, APA/MLA citation helper functions, DOI management, Zenodo publication, arXiv submission preparation, GitHub releases, PyPI and TestPyPI package distribution, static-site deployment to GitHub…
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
infrastructure-reference-citation
BibTeX read/write/convert that matches the syntax/semantics of projects/templates/templatecodeproject/manuscript/references.bib (consumed by Pandoc with --natbib -- see infrastructure/rendering/pdfcombinedrenderer.py). Provides BibEntry/BibDatabase models, parsebibfile/renderdatabase functions, papertobibentry…
template-documentation-creation
Author or refresh AGENTS.md and README.md for template directories — accurate commands, Mermaid where helpful, link generated/activeprojects.md. USE WHEN folder needs AGENTS, README audit, doc contract fix, or signposting after code change — even without documentationcreation prompt.
Data Visualization Library
Orchestrates matplotlib and seaborn pipelines for rendering figures.
cost-tracker
Track LLM API spend per session and task. Estimate token usage across providers. Warn before you blow your budget.