emem-eudr-due-diligence

emem-eudr-due-diligence is a skill for Claude Code from Vortx-AI/emem. It costs 154 tokens per session (2,159 once invoked), scanned A, original, Apache-2.0.

A tool that creates a signed Due Diligence Statement for the European Union Deforestation Regulation, a law requiring evidence that certain commodities are not linked to recent deforestation. It checks production plots against forest-loss data, but does not cover every required legal or forest-degradation check.

In plain words
What is it for?
Use it to evaluate production plots, commodities, and quantities; produce a signed statement covering location and deforestation evidence; and retain the result for compliance work.
Why use it?
Preparing this evidence by hand can make it difficult to check plot locations and forest-loss history consistently. The result also states which parts of the regulation it does not assess, so operators know what remains to be reviewed.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the emem plugin — 19 skills, 1 MCP server shipped together

Good fit Use it to evaluate production plots, commodities, and quantities; produce a signed statement covering location and deforestation evidence; and retain the result for compliance work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vortx-ai/emem/emem-eudr-due-diligence
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 Vortx-AI/emem --skill emem-eudr-due-diligence
Clone the repo
git clone --depth 1 https://github.com/Vortx-AI/emem

Made for: Claude Code.

Or install emem, the plugin that ships this one along with the rest of its 19 skills, 1 MCP server.

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 emem-eudr-due-diligence

README.md
[![agentmods](https://agentmods.dev/badge/skills/vortx-ai/emem/emem-eudr-due-diligence/github.svg)](https://agentmods.dev/skills/vortx-ai/emem/emem-eudr-due-diligence)
Your own site
<a href="https://agentmods.dev/skills/vortx-ai/emem/emem-eudr-due-diligence"><img src="https://agentmods.dev/badge/skills/vortx-ai/emem/emem-eudr-due-diligence/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 emem-eudr-due-diligence

Your own site · 80×15
<a href="https://agentmods.dev/skills/vortx-ai/emem/emem-eudr-due-diligence"><img src="https://agentmods.dev/badge/skills/vortx-ai/emem/emem-eudr-due-diligence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 154 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,159 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00154 $0.02159
Opus 5.5 $0.00062 $0.00864
Sonnet 5.5 $0.00031 $0.00432
Haiku 4.5 $0.00015 $0.00216

Measured 6d ago against content hash 6963d884a873, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

emem-eudr-due-diligence scanned grade A with 1 finding 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 6d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sf -m 300 -X POST https://emem.dev/v1/eudr_dds \
plugins/emem/skills/emem-eudr-due-diligence/SKILL.md · 145 lines

How it starts

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

emem-eudr-due-diligence

Network use. The commands in this skill send and receive JSON (and, where a step says so, an image or a raster file) to https://emem.dev only, the service the plugin's MCP server connects to. Nothing they download is executed. The files under scripts/ read local files and make no network calls.

POST /v1/eudr_dds (MCP emem_eudr_dds) evaluates plots against the Regulation's forest definition (10 % canopy, 0.5 ha, 5 m) and returns a signed envelope an operator can keep as evidence. It covers the geolocation and deforestation parts of Annex II. It does not cover legality (Article 9(1)(b)) or forest degradation (Article 2(7)), and the response says so in legality_disclaimer and degradation_disclaimer. Pass both on.

The request

curl -sf -m 300 -X POST https://emem.dev/v1/eudr_dds \
  -H 'content-type: application/json' \
  -d '{"operator": {"name": "Example Cocoa Importer"},
       "plots": [{"plot_id": "CIV-001",
                  "geometry_geojson": {"type": "Point", "coordinates": [-5.5471, 6.8276]},
                  "country_of_production": "CIV",
                  "commodity_hs": "180100",
                  "quantity_kg": 1200}]}' > dds.json

Per plot: geometry_geojson (a Polygon for plots over 4 ha; a Point is allowed for 4 ha or less, except cattle, per Article 2(28); or {"bbox":[w,s,e,n]}), country_of_production (ISO 3166-1 alpha-3), commodity_hs (HS-6 or longer, checked against Annex I) and quantity_kg. Optional: request_visual_evidence: true adds a year-by-year Sentinel-2 NDVI and Sentinel-1 backscatter timeline with scene links, and several minutes of upstream reads. Top level: cut_off_date (default 2020-12-31), forest_baseline_override (jrc_gfc2020_v3, hansen_only, both), max_cells_per_plot (auto-derived from polygon area when omitted). The full schema is GET https://emem.dev/v1/schemas/eudr_dds.json.

A cold plot can take minutes and can fail with source_fetch_failed naming the slow tile. Warm it first with a recall on one cell of the plot:

Read the full file on GitHub · 145 lines

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. 6d ago Changed · +4 lines 6963d884a873
  2. 7d ago Changed · +2 lines 11c93b2d4832
  3. 8d ago First seen · 139 lines · 154 tokens per session scan A 1228dfc6f408

Subscribe to this mod's changes

emem-eudr-due-diligence is a skill published in the GitHub repository Vortx-AI/emem (64 stars, last pushed 4d ago), licensed Apache-2.0. It adds 154 tokens to every session and 2,159 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-29.

Related

Other skills, from other repositories

shadow-perception-r-ds

Pre-publish council for R data-science analyses. Five voices review a .R / .Rmd / .qmd file for reproducibility (seed / renv / sessionInfo), fairness (ECOA §701 / GDPR Art. 9 protected classes), statistical rigor (p-hacking / multiple comparisons without p.adjust), data provenance (local vs remote sources), and output…

alex-jb/shadow-perception-mcp · 116 tokens

analytical-method-validation

Plans, executes, and documents validation, verification, and transfer of analytical procedures under the governing framework - ICH Q2(R2) and Q14, USP / / , ICH M10 bioanalytical, CLSI EP, or ISO/IEC 17025. Use for HPLC, LC-MS/MS, GC, CE, ICP-MS, dissolution, qNMR, qPCR, NIR, and ligand binding or cell-based assays…

K-Dense-AI/scientific-agent-skills · 281 tokens

agent-memory-discipline

Rules for when an agent should recall from long-term memory before acting and when it should save decisions, corrections and failures afterwards. Works with any memory backend.

sickn33/agentic-awesome-skills · 36 tokens

auditing-part11-trails

Generates and verifies 21 CFR Part 11-style audit trails — who/what/when, electronic signatures, and tamper-evidence — for OpenMed pipelines in GxP and clinical-trial (GCP) settings. Use when the user runs OpenMed in a regulated/validated environment and needs an attributable, time-stamped, tamper-evident record of…

maziyarpanahi/openmed · 222 tokens

generating-synthetic-surrogates

Replace detected PHI with realistic, type-matched fake values in OpenMed so clinical notes stay readable and parseable instead of full of [REDACTED] markers. Use when the user wants surrogate names, MRNs, addresses, or dates rather than opaque masks, needs consistent fake identities across a document, must keep notes…

maziyarpanahi/openmed · 145 tokens

shifting-clinical-dates

Apply consistent per-patient date shifting in OpenMed that preserves intervals between events while satisfying HIPAA Safe Harbor's date rule. Use when the user needs to de-identify dates but keep temporal structure for research, shift all dates by the same offset per patient, preserve days-between-events for survival…

maziyarpanahi/openmed · 135 tokens