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.
git clone --depth 1 https://github.com/DCS-Premium-Freight-SRL/claude-for-freightWrote 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/commands/dcs-premium-freight-srl/claude-for-freight/cargo-calc)<a href="https://agentmods.dev/commands/dcs-premium-freight-srl/claude-for-freight/cargo-calc"><img src="https://agentmods.dev/badge/commands/dcs-premium-freight-srl/claude-for-freight/cargo-calc/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/commands/dcs-premium-freight-srl/claude-for-freight/cargo-calc"><img src="https://agentmods.dev/badge/commands/dcs-premium-freight-srl/claude-for-freight/cargo-calc.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.00046 | $0.00306 |
| Opus 5 | $0.00023 | $0.00153 |
| Sonnet 5 | $0.00009 | $0.00061 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
cargo-calc 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 12d 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.
What it actually says
/freight-forwarding:cargo-calc
Triggers the cargo-calculation skill
directly.
Usage
/freight-forwarding:cargo-calc
Then provide the cargo details in any natural form:
4 pallets 120×80×140 cm, 250 kg each, air freight
Or structured:
pieces: 4 dimensions per piece: 120 × 80 × 140 cm weight per piece: 250 kg mode: air
You can also paste an email containing the cargo specs — the skill extracts.
What you get back
A summary with chargeable weight, CBM, freight ton, LDM, and the dominant factor (weight vs volume). See the skill for the full output format.
Notes
- If the practice profile is missing, you'll be prompted to confirm the IATA divisor (default 6000) and units (default cm/kg) once.
- The skill computes; it doesn't quote rates. To go from chargeable weight
to a quote, you need a rate connector (
cargo.one,WebCargo) or your rate sheet.
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.
- 12d ago First seen · 42 lines · 46 tokens per session scan A 760ea9a4dc4e
cargo-calc is a command published in the GitHub repository DCS-Premium-Freight-SRL/claude-for-freight (8 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 306 once invoked, about $0.0002 per session on Opus 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.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
fix
Universal debugging and fix application with semantic code analysis.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
tour
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit).