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 run-fluid-inspection-checklistgit 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/run-fluid-inspection-checklist)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/run-fluid-inspection-checklist"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-fluid-inspection-checklist/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/run-fluid-inspection-checklist"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-fluid-inspection-checklist.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.01456 |
| Opus 5 | $0.00023 | $0.00728 |
| Sonnet 5 | $0.00009 | $0.00291 |
| Haiku 4.5 | $0.00005 | $0.00146 |
Grade A, and why
run-fluid-inspection-checklist 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Fluid Inspection Checklist
Inspect all vehicle fluids systematically — checking level and condition for each system — to identify leaks, contamination, and degradation before they cause mechanical failure.
Why This Is Best Practice
Why best: Fluid inspection catches leaks, contamination, and degradation before they cause catastrophic mechanical failure, at near-zero cost and time. Adopted by: SAE International and automotive OEM owner's manuals mandate fluid checks as the cornerstone of preventive maintenance. AAA recommends monthly fluid checks; all major service chains (Jiffy Lube, Valvoline) base their service intervals on fluid inspection findings. Rental car companies and fleet operators run fluid checks at every fuel stop. Impact: Engine oil starvation (running 2+ quarts low) is the leading cause of catastrophic engine failure — a $5,000–$15,000 repair from a $0 inspection. Contaminated coolant causes corrosion and overheating; degraded brake fluid absorbs moisture, reducing boiling point and brake effectiveness. The majority of preventable mechanical failures have fluid condition or level as a contributing cause.
Steps
1. Engine oil — check level and condition
When to check: engine cold (off for 10+ min) for accurate dipstick reading.
Level check:
- Pull dipstick, wipe clean, reinsert fully, pull again
- Read level against MIN/MAX marks — should be at or near MAX
- Low by 1 quart = add 1 quart of the grade specified in the owner's manual (e.g., 5W-30); do not overfill above MAX
Condition check:
- Color should be amber to dark brown
- Black, gritty, or milky (creamy tan) oil is abnormal
- Black + gritty = overdue for change; change immediately
- Milky/creamy = coolant contamination (head gasket failure); do not drive; seek diagnosis
Change interval: consult owner's manual; modern synthetic oil is typically 7,500–10,000 miles; older conventional oil 3,000–5,000 miles. Never exceed manufacturer interval.
2. Coolant (antifreeze) — check level and freeze protection
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 · 97 lines · 47 tokens per session scan A e832d610bc18
run-fluid-inspection-checklist is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 23d ago), licensed MIT. It adds 47 tokens to every session and 1,456 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.