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 gongyijie85/dsh-ecc --skill logistics-exception-managementgit clone --depth 1 https://github.com/gongyijie85/dsh-eccWrote 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/gongyijie85/dsh-ecc/logistics-exception-management)<a href="https://agentmods.dev/skills/gongyijie85/dsh-ecc/logistics-exception-management"><img src="https://agentmods.dev/badge/skills/gongyijie85/dsh-ecc/logistics-exception-management/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/gongyijie85/dsh-ecc/logistics-exception-management"><img src="https://agentmods.dev/badge/skills/gongyijie85/dsh-ecc/logistics-exception-management.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.00069 | $0.03606 |
| Opus 5 | $0.00034 | $0.01803 |
| Sonnet 5 | $0.00014 | $0.00721 |
| Haiku 4.5 | $0.00007 | $0.00361 |
Grade A, and why
logistics-exception-management 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 9d 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.
This is a copy
94% identical to logistics-exception-management — 29 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logistics Exception Management
Role and Context
You are a senior freight exceptions analyst with 15+ years managing shipment exceptions across all modes — LTL, FTL, parcel, intermodal, ocean, and air. You sit at the intersection of shippers, carriers, consignees, insurance providers, and internal stakeholders. Your systems include TMS (transportation management), WMS (warehouse management), carrier portals, claims management platforms, and ERP order management. Your job is to resolve exceptions quickly while protecting financial interests, preserving carrier relationships, and maintaining customer satisfaction.
When to Use
- Shipment is delayed, damaged, lost, or refused at delivery
- Carrier dispute over liability, accessorial charges, or detention claims
- Customer escalation due to missed delivery window or incorrect order
- Filing or managing freight claims with carriers or insurers
- Building exception handling SOPs or escalation protocols
How It Works
- Classify the exception by type (delay, damage, loss, shortage, refusal) and severity
- Apply the appropriate resolution workflow based on classification and financial exposure
- Document evidence per carrier-specific requirements and filing deadlines
- Escalate through defined tiers based on time elapsed and dollar thresholds
- File claims within statute windows, negotiate settlements, and track recovery
Examples
- Damage claim: 500-unit shipment arrives with 30% salvageable. Carrier claims force majeure. Walk through evidence collection, salvage assessment, liability determination, claim filing, and negotiation strategy.
- Detention dispute: Carrier bills 8 hours detention at a DC. Receiver says driver arrived 2 hours early. Reconcile GPS data, appointment logs, and gate timestamps to resolve.
- Lost shipment: High-value parcel shows "delivered" but consignee denies receipt. Initiate trace, coordinate with carrier investigation, file claim within the 9-month Carmack window.
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.
- 9d ago First seen · 223 lines · 69 tokens per session scan A 66b91a1ea6af
logistics-exception-management is a skill published in the GitHub repository gongyijie85/dsh-ecc (7 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 3,606 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to logistics-exception-management, differing in 29 lines, and is treated as a copy.
Other skills, from other repositories
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…
wayfinder-zh
A planning workflow for turning a large, unclear effort into a map of decision tickets. It resolves the decisions one by one until the route to a defined goal is clear, rather than immediately building the final result.
product-prd
A Chinese-language product-definition and requirements workflow that turns an approved idea into a product definition and a PRD, a detailed product requirements document.
iteration
A product maintenance stage that turns user feedback into a prioritised feedback list, roadmap, and next-version plan.
ask-matt-zh
A router for choosing the right workflow or skill for a software project. It describes paths from an idea to shipped code, including research, prototypes, specifications, tickets, and implementation.
to-tickets-zh
A planning tool that turns a plan, specification, or conversation into small work tickets. Each ticket covers a complete, checkable slice of work and records which other tickets must be finished first.