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 jeffreytse/grimoire-core --skill diagnose-brake-system-problemgit clone --depth 1 https://github.com/jeffreytse/grimoire-coreWrote 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/jeffreytse/grimoire-core/diagnose-brake-system-problem)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/diagnose-brake-system-problem"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/diagnose-brake-system-problem/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/jeffreytse/grimoire-core/diagnose-brake-system-problem"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/diagnose-brake-system-problem.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.00039 | $0.01248 |
| Opus 5 | $0.00019 | $0.00624 |
| Sonnet 5 | $0.00008 | $0.00250 |
| Haiku 4.5 | $0.00004 | $0.00125 |
Grade A, and why
diagnose-brake-system-problem 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 10d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose Brake System Problem
Identify brake system faults from symptoms and visual inspection to determine urgency, root cause, and whether the vehicle is safe to drive.
Why This Is Best Practice
Adopted by: NHTSA safety enforcement, ASE-certified brake technicians (A5 specialty), DOT commercial vehicle inspection standards, AAA Approved Auto Repair brake service protocols
Impact: Brake system failure causes 22% of vehicle crash fatalities annually (NHTSA); correct diagnosis reduces unnecessary rotor replacement (34% of brake jobs replace rotors that meet spec, per ASE data); catching hydraulic failure early prevents total brake loss
Why best: FMVSS 105 mandates dual-circuit hydraulic systems; understanding the system's redundancy and failure modes enables accurate symptom-to-fault mapping before any vehicle is dismantled
Sources: NHTSA FMVSS 105 "Hydraulic and Electric Brake Systems"; ASE "Automobile Test A5 Brakes" certification curriculum; NHTSA "Brakes" vehicle safety campaign
Steps
-
Classify urgency from symptoms — DO NOT DRIVE: brake pedal goes to the floor, brake warning light on, vehicle pulls severely during braking, grinding metal-on-metal. DRIVE CAUTIOUSLY (1–2 days): pulsation, squeal, soft pedal without total loss. SCHEDULE SOON: low-pitched squeal intermittently, dust/debris visible on wheel.
-
Inspect brake warning lights — Red brake light: parking brake engaged OR low fluid level/system pressure loss (hydraulic fault). Amber ABS light: ABS module or wheel speed sensor fault (base brakes still function). Both lights simultaneously: potentially total brake system fault — do not drive.
-
Test pedal feel with engine off then on — Engine off: pump pedal 3–4 times; should become firm. Engine on: pedal should drop slightly then firm up (vacuum booster test). Pedal stays low or drops slowly to floor under steady pressure: hydraulic leak or failed master cylinder.
-
Check brake fluid level and color — Low fluid = worn pads (normal) OR leak (critical — inspect). Dark brown/black fluid = overdue change (moisture contamination). Milky fluid = coolant contamination (rare, internal master cylinder failure). Top up only with OEM-specified DOT rating; never mix DOT ratings.
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.
- 10d ago First seen · 60 lines · 39 tokens per session scan A 56fc6471f354
diagnose-brake-system-problem is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 21d ago), licensed MIT. It adds 39 tokens to every session and 1,248 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 skills, from other repositories
performance-profiling
CPU, memory, network bottleneck analysis — systematic performance investigation.
power-bi-performance-troubleshooting
Systematic Power BI performance troubleshooting prompt for identifying, diagnosing, and resolving performance issues in Power BI models, reports, and queries.
refactor
Systematic code refactoring to improve maintainability without changing behavior. Use when asked to "refactor this", "clean up this code", "improve code quality", "simplify this", "reduce complexity", or "eliminate code smells". Always preserves existing behavior.
extension-audit-methodology
Systematic 5-dimension audit framework for VS Code extensions — debug hygiene, dead code, performance, menu validation, dependency cleanup.
refactoring-patterns
Safe transformations — same behavior, better structure.
universal-audit-pattern
Systematic project audit pattern — version consistency, terminology, fact inventory, cross-references.