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 hos-eld-data-transfer-at-roadsidegit 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/hos-eld-data-transfer-at-roadside)<a href="https://agentmods.dev/skills/x3allamerican/skills/hos-eld-data-transfer-at-roadside"><img src="https://agentmods.dev/badge/skills/x3allamerican/skills/hos-eld-data-transfer-at-roadside/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/hos-eld-data-transfer-at-roadside"><img src="https://agentmods.dev/badge/skills/x3allamerican/skills/hos-eld-data-transfer-at-roadside.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.00042 | $0.00678 |
| Opus 5.5 | $0.00017 | $0.00271 |
| Sonnet 5.5 | $0.00008 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
hos-eld-data-transfer-at-roadside 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ELD Data Transfer at Roadside
When an inspector requests ELD records, the driver must transmit the prior 7 days plus the current day of duty data via one of THREE methods § 395.20 requires the ELD to support:
Required transfer methods (all 3)
- Wireless web services — driver enters inspector code in ELD; data is uploaded to FMCSA server, inspector retrieves
- Email (web mail) — driver sends email; inspector retrieves the link
- USB 2.0 — physical USB drive supplied by inspector; driver writes to drive
- Bluetooth — driver pairs phone/tablet; inspector retrieves
The driver chooses the method most reliable for the location (some rural inspection points have no cellular).
What data is transmitted
- 7 days + current day of RODS
- All edits, annotations, and malfunction history
- Unidentified driving events
- ELD output file (eRODS XML format per § 395.24)
Common failure modes
- Wireless transfer fails (no signal) → driver MUST be able to do USB or Bluetooth or display the records on the device screen + print
- Inspector code rejected by ELD → carrier-side issue, escalate to vendor immediately
- eRODS file rejected as malformed → ELD has a software bug, vendor must patch (logged as malfunction in the interim)
Driver training on transfer
Most carriers under-train drivers on the transfer procedure. The driver must:
- Open the ELD app
- Tap "Roadside Inspection" or equivalent
- Receive inspector code (verbal)
- Choose transfer method
- Confirm transmission successful
Common audit finding
Inspector marks "data transfer failure" — adds to HOS BASIC. Often a driver-training issue, not an ELD malfunction. Audit log post-incident.
CFR citations
- 49 CFR § 395.20
- 49 CFR § 395.22(b)
How Compass surfaces this
This skill is searchable in the Compass Ask interface and runs against the carrier's actual fleet data when invoked from within the relevant tracker. It is read-only — no actions are taken without explicit user approval.
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 · 59 lines · 42 tokens per session scan A 3c007e407774
hos-eld-data-transfer-at-roadside is a skill published in the GitHub repository x3allamerican/skills (3 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 678 once invoked, about $0.0002 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.
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.
Audit and normalize SPDX license headers before releasing or open-sourcing a repository
Use REUSE when an agent needs file-level licensing clarity instead of guessing from a single top-level LICENSE file. The agent checks compliance, adds or verifies SPDX headers, pulls missing license texts into LICENSES/, and produces a concrete remediation list or SPDX export.