calculate-tire-wear-assessment

calculate-tire-wear-assessment is a skill for Claude Code from jeffreytse/grimoire-core. It costs 40 tokens per session (1,353 once invoked), scanned A, original, MIT.

A procedure for checking tire condition, including tread depth, wear patterns, remaining safe life, and replacement needs.

In plain words
What is it for?
Assessing tires for safety and legal limits, deciding when to replace them, and investigating uneven tread wear.
Why use it?
It helps identify both unsafe tires and possible causes of uneven wear, such as alignment, inflation, or suspension problems.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-automotive plugin — 16 skills shipped together

Good fit Assessing tires for safety and legal limits, deciding when to replace them, and investigating uneven tread wear.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/calculate-tire-wear-assessment
Install

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.

Any agent
npx skills add jeffreytse/grimoire-core --skill calculate-tire-wear-assessment
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-automotive, the plugin that ships this one along with the rest of its 16 skills.

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 calculate-tire-wear-assessment

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/calculate-tire-wear-assessment/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/calculate-tire-wear-assessment)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/calculate-tire-wear-assessment"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/calculate-tire-wear-assessment/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.

agentmods 80×15 button for calculate-tire-wear-assessment

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/calculate-tire-wear-assessment"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/calculate-tire-wear-assessment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,353 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.00040 $0.01353
Opus 5 $0.00020 $0.00677
Sonnet 5 $0.00008 $0.00271
Haiku 4.5 $0.00004 $0.00135

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

Security

Grade A, and why

calculate-tire-wear-assessment 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.

skills/automotive/maintenance/skills/calculate-tire-wear-assessment/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Calculate Tire Wear Assessment

Measure tread depth, interpret wear pattern type, calculate remaining safe life, and determine whether tires require immediate replacement using NHTSA safety thresholds and systematic wear pattern diagnosis.

Why This Is Best Practice

Why best: Tread depth thresholds and systematic wear-pattern diagnosis catch both the immediate safety risk (inadequate wet-traction) and the root cause (alignment, inflation, suspension) — replacing tires without fixing the cause just repeats the failure. Adopted by: NHTSA (National Highway Traffic Safety Administration) mandates minimum 2/32" tread depth in the US; EU regulations require 1.6mm (≈2/32"). AAA recommends proactive replacement at 4/32" for wet-weather safety. Fleet operators (UPS, FedEx, airline ground vehicles) use systematic tire assessment schedules to prevent blowout-related incidents. Impact: NHTSA data shows tires contribute to ~664 fatal crashes annually in the US — most due to worn tread, under-inflation, or damage. Wet stopping distance at 4/32" tread is 50% longer than at 8/32"; at 2/32" it doubles relative to new tires. Beyond safety, misidentifying the cause of uneven wear leads to repeat failure — worn tires are a symptom; the root cause (alignment, inflation, suspension) must also be corrected.

Steps

1. Measure tread depth

Tread depth gauge (most accurate): insert probe into tread groove at the shallowest point; read in 32nds of an inch (US) or mm (EU).

Penny test (emergency check): insert a US penny (Lincoln head down) into the tread. If you see the top of Lincoln's head, tread is ≤2/32" — replace immediately.

Quarter test: insert a US quarter (Washington head down). If you see the top of Washington's head, tread is ≤4/32" — replace soon; wet-weather performance is significantly compromised.

New tire tread depth: typically 10/32" to 11/32" for passenger; 14/32" for light truck.

Measure at 3 points across the tread width (inner, center, outer) and at 4 locations around the circumference. Record all measurements.

Read the full file on GitHub · 88 lines

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. 12d ago First seen · 88 lines · 40 tokens per session scan A 8c4ede507b9f

Subscribe to this mod's changes

calculate-tire-wear-assessment is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 24d ago), licensed MIT. It adds 40 tokens to every session and 1,353 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.