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-suspension-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-suspension-problem)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/diagnose-suspension-problem"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/diagnose-suspension-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-suspension-problem"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/diagnose-suspension-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.00045 | $0.01396 |
| Opus 5 | $0.00023 | $0.00698 |
| Sonnet 5 | $0.00009 | $0.00279 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
diagnose-suspension-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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose Suspension Problem
Systematically identify failing suspension and steering components through symptom analysis, visual inspection, road testing, and component-specific tests — preventing misdiagnosis and unnecessary parts replacement.
Why This Is Best Practice
Why best: Symptom-to-component mapping is systematic, not guesswork — matches ASE-certified diagnostic method. Adopted by: ASE (Automotive Service Excellence) A4 certification covers suspension and steering diagnosis as a distinct domain. Monroe and KYB (major shock absorber manufacturers) publish suspension diagnostic flowcharts used industry-wide by service technicians. Hunter Engineering's wheel alignment systems (used by 90% of US tire shops) require suspension diagnosis before alignment service. Impact: Suspension components rarely fail in isolation. A worn stabilizer bar link causes a thumping noise over bumps; worn ball joints cause wandering and clunking; weak struts cause bouncing and extended braking distances. Misidentifying the symptom leads to replacing the wrong component — the problem recurs and the old part was wasted. Systematic symptom-to-component mapping eliminates guesswork.
Steps
1. Categorize the presenting symptom
Each symptom points to a specific component set:
| Symptom | Likely component area |
|---|---|
| Pull to one side (consistent) | Tire pressure difference, alignment (camber/toe), brake drag |
| Pull to one side (braking only) | Brake caliper sticking, brake hose collapse |
| Vehicle wanders / needs constant correction | Tie rod ends, loose steering gear, alignment (toe) |
| Bounce / excessive body motion | Shock absorbers or struts (most common) |
| Nose dive under braking | Front struts worn |
| Clunk over bumps (front) | Sway bar end links, strut top mounts, ball joints |
| Clunk over bumps (rear) | Sway bar bushings, control arm bushings |
| Grinding/creaking in turns | CV axle joint, wheel bearing |
| Steering wheel vibration at speed | Wheel balance, worn tie rod ends, loose wheel hub |
| Uneven tire wear | Alignment (see tire wear pattern) |
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 · 98 lines · 45 tokens per session scan A 3fdfe5757d87
diagnose-suspension-problem is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 21d ago), licensed MIT. It adds 45 tokens to every session and 1,396 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
semantic-model-disambiguation
Analyze Power BI semantic models for column-level overlaps that confuse Copilot and Fabric data agents. Detect ambiguity, review with domain expert, apply fixes via MCP.
infrastructure-as-code
Domain: DevOps & Cloud Engineering.
prompt-2-data
Generate comprehensive synthetic relational data for any specified subject with multiple normalized CSV files maintaining referential integrity.
academic-paper-drafting
End-to-end academic paper drafting for CHI, HBR, journals, and conferences with venue-specific templates, drafting workflows, and revision strategies.
research-first-development
Build knowledge bases that build software — research before code, teach before execute.
agent-governance
Patterns for adding safety, trust, and policy enforcement to AI agent systems -- control which tools agents can call, what content they process, and maintain accountability through audit trails.