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 x3allamerican/skills --skill eld-mandate-compliancegit clone --depth 1 https://github.com/x3allamerican/skillsWrote 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/x3allamerican/skills/eld-mandate-compliance)<a href="https://agentmods.dev/skills/x3allamerican/skills/eld-mandate-compliance"><img src="https://agentmods.dev/badge/skills/x3allamerican/skills/eld-mandate-compliance/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/x3allamerican/skills/eld-mandate-compliance"><img src="https://agentmods.dev/badge/skills/x3allamerican/skills/eld-mandate-compliance.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.00104 | $0.01366 |
| Opus 5.5 | $0.00042 | $0.00546 |
| Sonnet 5.5 | $0.00021 | $0.00273 |
| Haiku 4.5 | $0.00010 | $0.00137 |
Grade A, and why
eld-mandate-compliance 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 1mo 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ELD Mandate Compliance — 49 CFR 395.20-38
The ELD Final Rule became effective Dec 18, 2017 for new ELDs and Dec 16, 2019 for AOBRD-using fleets to fully transition. As of 2026, virtually all interstate CMV drivers must use a registered ELD.
Who must use an ELD
Drivers must use a registered ELD if all of:
- Required to maintain a record of duty status (RODS) under 49 CFR 395, AND
- Operating an interstate CMV requiring a CDL.
Exemptions from the ELD rule
A driver does NOT have to use an ELD if:
- Short-haul (49 CFR 395.1(e)(1) or (e)(2)) — operates within 150 air-mile radius, returns to work-reporting location within 14 hours, etc.
- 8-day exception — uses paper logs for 8 or fewer days in any 30-day period.
- Driveaway-towaway — vehicle is the commodity being delivered.
- Pre-2000 engine — operating a CMV manufactured before model year 2000 (engine model year governs).
ELD registration
ELDs must be on the FMCSA's Registered ELDs list at eld.fmcsa.dot.gov. Manufacturers self-certify; FMCSA accepts the self-certification but reserves right to revoke. Some ELDs have been revoked — always verify your ELD is currently listed.
Malfunction handling (49 CFR 395.34)
If an ELD malfunctions, the driver must:
- Note the malfunction on the log
- Reconstruct previous 7 days on paper if not already recorded
- Continue manual paper logs until the ELD is repaired
- Carrier has 8 days from notification to repair/replace OR
- Submit a malfunction notice to FMCSA requesting an extension
If a driver experiences a malfunction during a roadside inspection, they should display the device + show paper logs covering the relevant period.
ELD data file (eRODS)
When inspected at roadside, the driver transfers the ELD data to the inspector via:
- Web service — driver enters inspector's email
- USB drive — physical handoff
- Bluetooth — wireless transmission
The ELD must support at least one method. Some ELDs support both; FMCSA's eRODS app reads either format.
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.
- 1mo ago First seen · 110 lines · 104 tokens per session scan A 44da39294883
eld-mandate-compliance is a skill published in the GitHub repository x3allamerican/skills (3 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 104 tokens to every session and 1,366 once invoked, about $0.0004 per session on Opus 5.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
disclosure-page-generator
Deprecated compatibility entry for Disclosure Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Disclosure Page.
email-lifecycle-send-check
Checks a drafted email flow or broadcast before it is loaded: flow logic and exits, overlaps, offer depth and codes, stock, claims, consent and legal footer, SMS rules, rendering, voice and AI-copy tells, and the goal metric. Returns a pass / fixed / open-question table. Use alone when you already have the finished…
lov-china-website-filing
A workflow for preparing and launching websites in mainland China, including ICP filing and public-security filing. ICP filing is the registration required for many mainland websites, while public-security filing is a separate police registration.
healthcare-providers-verify
Validates practitioner credentials and license status against the NPI registry. Cross-references specialties, credentials, and practice addresses against official records. Returns Verified / Partially Verified / Unverified / Flagged per practitioner with mismatch details and source URLs. Triggers: "verify these…
performing-soc2-type2-audit-preparation
Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security…
python-packaging-license-finder
Use this skill to deterministically find license information for Python packages by checking PyPI metadata first, then falling back to Git repository LICENSE files using shallow cloning.