traffic-damage-calc

traffic-damage-calc is a command for Claude Code from llamadrive/bengo-toolkit. It costs 25 tokens per session (467 once invoked), scanned A, original, MIT.

A calculator for estimating compensation for bodily injuries from traffic accidents under Japan’s commonly used “Red Book” legal standards.

In plain words
What is it for?
Use it to calculate treatment costs, lost income,慰謝料 compensation, attorney fees, delayed-payment interest, and reductions for shared fault.
Why use it?
It applies published tables and coefficients consistently instead of asking a language model to guess the amount.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is Read, Glob, Bash(python3 skills/traffic-damage-calc/calc.py:*), Bash(python3 skills/traffic-damage-calc/test_calc.py:*), Bash(python3 skills/_lib/workspace.py:*.

Part of the bengo-toolkit plugin — 15 skills, 25 commands, 3 MCP servers shipped together

Good fit Use it to calculate treatment costs, lost income,慰謝料 compensation, attorney fees, delayed-payment interest, and reductions for shared fault.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/llamadrive/bengo-toolkit
agentmods
npx agentmods add commands/llamadrive/bengo-toolkit/traffic-damage-calc

Made for: Claude Code.

Or install bengo-toolkit, the plugin that ships this one along with the rest of its 15 skills, 25 commands, 3 MCP servers.

Wrote 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.

agentmods badge for traffic-damage-calc

README.md
[![agentmods](https://agentmods.dev/badge/commands/llamadrive/bengo-toolkit/traffic-damage-calc.svg)](https://agentmods.dev/commands/llamadrive/bengo-toolkit/traffic-damage-calc)
Your own site
<a href="https://agentmods.dev/commands/llamadrive/bengo-toolkit/traffic-damage-calc"><img src="https://agentmods.dev/badge/commands/llamadrive/bengo-toolkit/traffic-damage-calc.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 467 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00467
Opus 5 $0.00013 $0.00234
Sonnet 5 $0.00005 $0.00093
Haiku 4.5 $0.00003 $0.00047

Measured 7d ago against content hash e6d19b07dfb4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

traffic-damage-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 7d 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.

commands/traffic-damage-calc.md · 24 lines

What it actually says

交通事故による人身損害の賠償額を、日弁連交通事故相談センター東京支部編「民事交通事故訴訟損害賠償額算定基準」(通称「赤い本」)の基準に従って計算する。LLM の推論ではなく、判例と実務で確立した表値・係数を用いた決定論的計算。

計算項目

  • 積極損害(治療費・交通費・装具費・入院雑費・付添看護費)
  • 消極損害(休業損害・後遺障害逸失利益・死亡逸失利益、Leibniz 係数による中間利息控除)
  • 慰謝料(入通院・後遺障害・死亡、赤い本別表 I/II 準拠)
  • 弁護士費用(10%、判例実務)
  • 遅延損害金(年3%、改正民法 404 条)
  • 過失相殺(民法 722 条 2 項)

$ARGUMENTS: 対話で入力するか、JSON ファイルを指定する。

使い方

対話形式で被害者・事故・治療情報を順次確認する。具体的な手順は skills/traffic-damage-calc/SKILL.md に従う。

まず skills/traffic-damage-calc/SKILL.md を Read ツールで読み込み、そこに記載された手順に従って実行する。

Changes

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.

  1. 7d ago First seen · 24 lines · 25 tokens per session scan A e6d19b07dfb4

Subscribe to this mod's changes

traffic-damage-calc is a command published in the GitHub repository llamadrive/bengo-toolkit (6 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 467 once invoked, about $0.0001 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.