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-cooling-system-failuregit 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-cooling-system-failure)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/diagnose-cooling-system-failure"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/diagnose-cooling-system-failure/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-cooling-system-failure"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/diagnose-cooling-system-failure.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.00049 | $0.01362 |
| Opus 5 | $0.00024 | $0.00681 |
| Sonnet 5 | $0.00010 | $0.00272 |
| Haiku 4.5 | $0.00005 | $0.00136 |
Grade A, and why
diagnose-cooling-system-failure 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose Cooling System Failure
Systematically pressure-test and inspect the cooling system to identify leaks, blockages, thermostat failure, or head gasket compromise before the engine is driven and damaged further.
Why This Is Best Practice
Why best: Pressure-testing before diagnosis isolates the true root cause (leak, thermostat, water pump, head gasket) instead of guessing — guessing on cooling failures risks catastrophic engine damage. Adopted by: ASE A1 Engine Repair certification dedicates a major section to cooling system diagnosis. Gates Corporation and Prestone publish industry-standard cooling system diagnostic guides used by shop technicians. All OEM service manuals require a pressure test before any coolant-related diagnosis or repair. Impact: Overheating is the most damaging condition a car engine can experience — one overheating event can warp cylinder heads ($1,000–$3,000), crack a head gasket ($1,500–$4,000), or seize bearings (total engine replacement: $3,000–$8,000). Many cooling system failures present identically in symptoms but have different root causes: a leaking hose, a stuck thermostat, a failed water pump, and a blown head gasket all cause overheating. Driving with any of these undiagnosed causes escalating damage.
Steps
1. Safety first — never open a hot radiator
A hot cooling system is pressurized to 15+ PSI. Opening the radiator cap or overflow reservoir on a hot engine ejects scalding coolant.
Rule: never open coolant system when engine is hot. Wait 30–60 minutes after shutdown, or wrap the cap in a thick cloth and open slowly, releasing pressure gradually before removing.
2. Observe the symptoms before touching anything
| Symptom | Initial suspects |
|---|---|
| Overheating (temp gauge high) | Thermostat stuck closed, low coolant, radiator blocked, water pump failure |
| Temperature gauge never reaches normal | Thermostat stuck open |
| Coolant disappearing without visible leak | Head gasket (internal leak), leaking heater core |
| White smoke from exhaust | Head gasket failure (coolant burning in combustion chamber) |
| Heater blowing cold (engine hot) | Low coolant level, thermostat stuck open, clogged heater core |
| Bubbling in coolant reservoir when engine running | Head gasket (combustion gases entering cooling system) |
| Milky oil on dipstick | Head gasket (coolant mixing with oil — critical; do not drive) |
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.
- 12d ago First seen · 107 lines · 49 tokens per session scan A 3ddb548a0666
diagnose-cooling-system-failure is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 23d ago), licensed MIT. It adds 49 tokens to every session and 1,362 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.
prompt-2-data
Generate comprehensive synthetic relational data for any specified subject with multiple normalized CSV files maintaining referential integrity.
infrastructure-as-code
Domain: DevOps & Cloud Engineering.
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.