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 dataq-crash-classificationgit 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/dataq-crash-classification)<a href="https://agentmods.dev/skills/x3allamerican/skills/dataq-crash-classification"><img src="https://agentmods.dev/badge/skills/x3allamerican/skills/dataq-crash-classification/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/dataq-crash-classification"><img src="https://agentmods.dev/badge/skills/x3allamerican/skills/dataq-crash-classification.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.00044 | $0.00633 |
| Opus 5.5 | $0.00018 | $0.00253 |
| Sonnet 5.5 | $0.00009 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
dataq-crash-classification 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DataQ Filing for Crash Classification Errors
Per § 390.5, a DOT-recordable crash requires: fatality, bodily injury requiring medical treatment off-scene, OR disabling damage requiring tow-away. Crashes missing these triggers are NOT recordable. Challenge them.
Common misclassification scenarios
- Crash with no injuries but tow-away (this IS recordable; not a challenge target)
- Crash with minor injuries where first aid was given on scene only — NOT recordable
- Crash with damage but vehicles were drivable — NOT recordable (tow-away requires inability to drive)
- Crash with passenger pre-existing condition — depends on what triggered medical treatment
- Crash where parties drove away but later sought medical treatment — typically NOT recordable (treatment must be away from scene immediately)
Evidence needed
- Police report (often shows injury status, tow-away status)
- Photos of damage
- Witness statements
- Medical records (if available, can show no immediate off-scene treatment)
- Vehicle inspection results
- Insurance claim records
Filing steps
- Go to fmcsa.dot.gov/DataQ
- Search for the crash record
- Challenge category: "Crash Classification"
- Subcategory: "Not DOT-recordable"
- Narrative explaining why crash does not meet § 390.5 triggers
- Upload evidence
Success rate
- Documentation clearly shows no qualifying trigger: ~70%
- Officer reasonably classified given on-scene info: ~30%
Compass support
Compass Accidents module:
- Cross-references your crash records against § 390.5 criteria
- Flags potentially non-recordable crashes
- Builds the DataQ challenge with evidence package
- Tracks reversal
CFR citations
- 49 CFR § 390.5
- FMCSA DataQ User Guide
How Compass surfaces this
Searchable in Compass Ask. Runs against the carrier's actual fleet data when invoked from the relevant tracker. Read-only; no actions without explicit user approval.
Built by X3 Compass
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 · 63 lines · 44 tokens per session scan A 3cc97a76dbce
dataq-crash-classification is a skill published in the GitHub repository x3allamerican/skills (3 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 633 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.