agricultural-engineer

agricultural-engineer is a skill for Claude Code, Codex from wonsukchoi/domain-experts. It costs 90 tokens per session (3,914 once invoked), scanned A, original, MIT.

An engineering guide for designing farm systems that handle water, crops, stored grain, waste, and machinery.

In plain words
What is it for?
Use it to size irrigation, drainage, waterways, tile systems, grain-bin walls, manure and nutrient systems, and related farm equipment.
Why use it?
It helps balance construction and operating costs against the risk of failure during peak crop water demand, full storage, or severe storms.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to size irrigation, drainage, waterways, tile systems, grain-bin walls, manure and nutrient systems, and related farm equipment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wonsukchoi/domain-experts/agricultural-engineer
Install

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.

Any agent
npx skills add wonsukchoi/domain-experts --skill agricultural-engineer
Clone the repo
git clone --depth 1 https://github.com/wonsukchoi/domain-experts

Made for: Claude Code, Codex.

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 agricultural-engineer

README.md
[![agentmods](https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/agricultural-engineer/github.svg)](https://agentmods.dev/skills/wonsukchoi/domain-experts/agricultural-engineer)
Your own site
<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/agricultural-engineer"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/agricultural-engineer/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 agricultural-engineer

Your own site · 80×15
<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/agricultural-engineer"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/agricultural-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,914 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.
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.00090 $0.03914
Opus 5 $0.00045 $0.01957
Sonnet 5 $0.00018 $0.00783
Haiku 4.5 $0.00009 $0.00391

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

Security

Grade A, and why

agricultural-engineer 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.

roles/agricultural-engineer/SKILL.md · 112 lines

How it starts

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

Agricultural Engineer

Identity

Designs irrigation, drainage, grain-storage structures, manure/nutrient management systems, and farm machinery systems, typically under a Professional Engineer license for anything bearing on structural or public-safety load (grain bins, waste storage structures, dams and impoundments). Works from soil survey data, hydrologic records, and crop water/nutrient requirements rather than architectural intent — the client is a biological and physical system (soil, crop, weather) that doesn't negotiate. The defining tension: capital a farm operation spends on a design margin it never needed is capital that can't buy the next input or piece of equipment, but a margin that's too thin fails exactly when the system is under the most load — peak ET during tasseling, a bin filled to capacity at harvest, a 24-hour storm — and a field failure (blown-out tile main, buckled bin wall, overtopped waste-storage berm) is discovered by the failure itself, not by an inspection ahead of it.

First-principles core

  1. A design storm or design flow is a statistical choice, not the biggest event on record. NRCS design criteria size a waterway or drainage outlet to a stated return period (commonly 10-year, 24-hour for cropland; higher where downstream consequence is severe) — this is an accepted annual exceedance probability, not a claim that a bigger storm won't come. Picking a return period is picking who bears the risk (the structure vs. the field) at a stated frequency.
  2. Bulk grain against a bin wall does not behave like a fluid. Wall friction carries part of the grain's weight vertically, so lateral pressure grows with depth then asymptotes toward a maximum (Janssen's equation) rather than increasing linearly the way hydrostatic pressure does — a bin wall designed on a hydrostatic assumption is overbuilt at depth and, more dangerously, can still be underbuilt near the eave where the linear and asymptotic curves are close together.
  3. Irrigation system capacity is set by the crop's peak-day demand, not its seasonal average. A system sized to deliver the average inches-per-week over the season runs a chronic deficit during the single highest-demand week (typically tasseling-silking for corn) — the average never has to keep the crop alive on the worst day, and the system does.
  4. Manure nitrogen is not commercial fertilizer nitrogen; only a fraction is available to the crop that season. Total N on a manure analysis includes organic N that mineralizes over years, not weeks — applying by total-N-equivalent to a fertilizer rate over-applies in year one, under-credits the following two seasons, and both errors show up as nutrient-management-plan noncompliance or nitrate loss, not as a visible field problem.
  5. Draining or ditching a wet area is a federal compliance question before it's a hydraulic one. Converting a wetland for agricultural production without an approved exemption or minimal-effect determination risks USDA program-benefit ineligibility (Swampbuster, 16 U.S.C. §3821) regardless of how sound the hydraulic design is — the permitting determination has to happen before the design proceeds, not after.

Read the full file on GitHub · 112 lines

Files

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.

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. 12d ago First seen · 112 lines · 90 tokens per session scan A 57fa7a7217f3

Subscribe to this mod's changes

agricultural-engineer is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 4d ago), licensed MIT. It adds 90 tokens to every session and 3,914 once invoked, about $0.0005 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

thesis-control

Use when AI-assisted thesis or manuscript edits risk claim drift, scope creep, loss of intended use, experiment-role promotion, or repeated revisions that fail to converge; provides author-intent control, lightweight or strict contracts, drift audits, revision escalation, and human gates.

yha9806/academic-writing-toolkit · 57 tokens

manuscript-reframe

Reframe report-like academic drafts into paper-form scientific arguments while preserving or explicitly renegotiating author intent; requires an approved old-versus-proposed spine, evidence and argument baselines, analysis-role control, and post-edit drift review.

yha9806/academic-writing-toolkit · 53 tokens

infrastructure-validation

Skill for the validation infrastructure module providing PDF validation, markdown validation, output integrity checks, link verification, documentation audits, issue categorization, and repository scanning. Use when validating research outputs, checking document quality, running audits, or verifying cross-references.

docxology/template · 54 tokens

provenance-dag

Content-addressed provenance DAG for research lineage tracking. Use for: recording which pipeline stage produced which artifact, querying edges between recorded nodes, running a DAG-wide review and validation pass. CLI: python -m infrastructure.provenance {list,record-artifact,review,validate}. Library…

docxology/template · 103 tokens

scientific-connectors

Search 8+ scientific databases through a uniform Connector interface. Use for: literature review, biology database queries, protein/PDB searches. CLI: python -m infrastructure.search.connectors {list-dbs,search}. Config: set queries in projects/{name}/manuscript/config.yaml connectorsearch: block. Orchestrator…

docxology/template · 87 tokens

infrastructure-search-literature

Paperclip-style multi-source literature search across arXiv, Crossref, local JSON corpora, and (opt-in) the Paperclip API. Provides Paper/SearchQuery/SearchResult data models, a LiteratureClient aggregator with per-backend failure isolation, DOI/arXiv-aware deduplication via mergepapers, deterministic JSON caching via…

docxology/template · 123 tokens