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-battery-charging-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-battery-charging-problem)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/diagnose-battery-charging-problem"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/diagnose-battery-charging-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-battery-charging-problem"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/diagnose-battery-charging-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.00047 | $0.01401 |
| Opus 5 | $0.00023 | $0.00700 |
| Sonnet 5 | $0.00009 | $0.00280 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
diagnose-battery-charging-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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose Battery and Charging Problem
Systematically test the battery, alternator, and charging circuit to identify the root cause of starting failures or electrical problems — preventing unnecessary parts replacement by following a test-first diagnostic sequence.
Why This Is Best Practice
Why best: A fixed test sequence — battery load test before alternator test before parasitic-drain test — catches the actual fault instead of guessing, because each stage's result depends on the previous stage being confirmed good first. Adopted by: ASE (Automotive Service Excellence) certification requires systematic charging system diagnosis as part of A6 Electrical/Electronic Systems competency. All major auto repair chains (Firestone, Jiffy Lube, Midas) offer free battery and alternator testing as a standard service. OBD-II scan tools used by professional technicians prioritize charging system voltage codes as primary electrical diagnostics. Impact: The most common diagnosis error is replacing the battery when the alternator is the fault — or replacing the alternator when the battery (unable to hold a charge) is masking a good alternator. AAA data shows that battery-related calls represent ~20% of roadside assistance requests. A systematic test sequence takes 10–15 minutes and eliminates guesswork, preventing the second-most expensive diagnostic error in automotive service: replacing good parts.
Steps
1. Gather symptoms before testing
Document the presenting complaint:
- Slow crank / click on start: battery, battery terminals, or starter
- No crank (complete silence): battery, terminals, ignition switch, neutral safety switch
- Engine starts, battery light illuminates: alternator or drive belt
- Battery repeatedly dies overnight: parasitic drain or battery can't hold charge
- Electrical accessories dim at idle: alternator undercharging
2. Visual inspection first
Before any electrical test:
- Check battery terminals: green/white corrosion indicates sulfation — clean with baking soda solution and wire brush before testing (corrosion increases resistance and mimics battery failure)
- Check battery case: cracks or bulging indicate internal failure — replace immediately
- Check alternator drive belt: frayed, cracked, or glazed belt prevents charging regardless of alternator condition
- Check ground cables: black cables from battery negative to chassis and engine block — loose ground causes widespread electrical symptoms
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 · 97 lines · 47 tokens per session scan A 426823c2b419
diagnose-battery-charging-problem is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 22d ago), licensed MIT. It adds 47 tokens to every session and 1,401 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.