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 millisa09/freight-quote-claude-skills --skill carrier-incident-reportgit clone --depth 1 https://github.com/millisa09/freight-quote-claude-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/millisa09/freight-quote-claude-skills/carrier-incident-report)<a href="https://agentmods.dev/skills/millisa09/freight-quote-claude-skills/carrier-incident-report"><img src="https://agentmods.dev/badge/skills/millisa09/freight-quote-claude-skills/carrier-incident-report/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/millisa09/freight-quote-claude-skills/carrier-incident-report"><img src="https://agentmods.dev/badge/skills/millisa09/freight-quote-claude-skills/carrier-incident-report.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.00167 | $0.01029 |
| Opus 5.5 | $0.00067 | $0.00412 |
| Sonnet 5.5 | $0.00033 | $0.00206 |
| Haiku 4.5 | $0.00017 | $0.00103 |
Grade A, and why
carrier-incident-report 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 2mo 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Carrier Incident Report
Documents carrier failures professionally and generates both a Word incident report and two draft emails — one to the carrier, one to the customer.
Step 1 — Gather Incident Facts
Extract the following from the conversation. Ask only for what's missing:
| Field | Required | Notes |
|---|---|---|
| Load / Pro Number | Yes | Your internal load reference |
| Carrier Name | Yes | Legal carrier name |
| MC / DOT Number | If known | |
| Driver Name | If known | |
| Driver Phone | If known | |
| Dispatcher Name / Contact | If known | |
| Origin | Yes | City, ST |
| Destination | Yes | City, ST |
| Commodity | Yes | What was being shipped |
| Pickup Date | Yes | |
| Delivery Date (scheduled) | Yes | |
| Violation / Failure Type | Yes | See categories below |
| Timeline of Events | Yes | What happened, in order, with times |
| Customer Name | Yes | Who the load was for |
| Financial Impact | If applicable | Detention, re-delivery costs, claims |
| Resolution Status | Yes | Open / Resolved / Pending |
Violation Categories
- Missed delivery appointment
- Driver unreachable / no check-ins
- GPS / tracking non-compliance
- Cargo damage or shortage
- Driver misrepresenting location
- Detention dispute
- Late pickup
- Re-brokering without consent
- Equipment failure or wrong equipment
- DOT / safety violation
- Other (specify)
Step 2 — Generate the Report
Using the gathered facts, produce:
A) Incident Report Document (Word .docx)
Structure:
CARRIER INCIDENT REPORT
[Broker Company] | [MC#] | [Date]
LOAD INFORMATION
- Load #, Carrier, MC#, Driver, Equipment
- Origin → Destination, Commodity, Pickup/Delivery dates
INCIDENT SUMMARY
- 2–3 sentence plain-language summary of what happened
TIMELINE OF EVENTS
- Bullet list: [Date/Time] — Event description
VIOLATION / FAILURE TYPE
- Category + specific details
FINANCIAL IMPACT
- Any costs incurred or at risk
RESOLUTION STATUS
- Current status and next steps
DOCUMENTATION
- Note any emails, calls, screenshots referenced
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.
- 2mo ago First seen · 156 lines · 167 tokens per session scan A 38b70d0def39
carrier-incident-report is a skill published in the GitHub repository millisa09/freight-quote-claude-skills (6 stars, last pushed 6mo ago), licensed MIT. It adds 167 tokens to every session and 1,029 once invoked, about $0.0007 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-08-31.
carrier-incident-report compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| carrier-incident-reportmillisa09/freight-quote-claude-skills | Skill | 6 | 6mo ago | MIT | A | 167 | Claude Code, Codex |
| fto-triageanthropics/claude-for-legal | Skill | 9.9k | 3d ago | Apache-2.0 | A | 81 | Claude Code |
| legal-holdanthropics/claude-for-legal | Skill | 9.9k | 3d ago | Apache-2.0 | A | 68 | Claude Code |
| specification-writingwanshuiyin/Auto-claude-code-research-in-sleep | Skill | 19k | 3d ago | MIT | A | 49 | Claude Code |
| terms-of-servicegenspark-ai/genoffice | Skill | 12k | 2d ago | Apache-2.0 | A | 32 | Claude Code, Codex |
| x-scorecardx-cmd/x-cmd | Skill | 4.7k | 7d ago | Apache-2.0 | A | 57 | Claude Code, Codex |
| gesellschaftsrechtliche-satzungen-agbKlotzkette/claude-fuer-deutsches-recht | Skill | 1.8k | yesterday | Apache-2.0 | A | 69 | Claude Code |