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 design-preventive-maintenance-schedulegit 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/design-preventive-maintenance-schedule)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-preventive-maintenance-schedule"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-preventive-maintenance-schedule/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/design-preventive-maintenance-schedule"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-preventive-maintenance-schedule.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.00029 | $0.00925 |
| Opus 5 | $0.00015 | $0.00463 |
| Sonnet 5 | $0.00006 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
design-preventive-maintenance-schedule 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 11d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Preventive Maintenance Schedule
Build a structured, interval-based maintenance plan that keeps a vehicle reliable, safe, and cost-efficient over its lifetime.
Why This Is Best Practice
Adopted by: AAA Approved Auto Repair network (7,000+ shops), OEM manufacturers (SAE International standards), NHTSA fleet safety programs, and U.S. Department of Transportation
Impact: Preventive maintenance reduces breakdown risk by 75%, extends engine life by 40-60%, and lowers total repair costs by an average of $1,200/year compared to reactive repair only (AAA, 2023)
Why best: Interval-based scheduling aligns with component wear cycles validated through OEM durability testing. It prevents cascading failures where one neglected item degrades adjacent systems.
Sources: AAA "Your Driving Costs" 2023; SAE J1082 maintenance interval standard; NHTSA vehicle maintenance recommendations
Steps
-
Gather baseline data — Collect vehicle year, make, model, trim, current mileage, and driving conditions (city/highway ratio, climate, towing use)
-
Pull the OEM service schedule — Locate the manufacturer's maintenance schedule in the owner's manual or OEM website; note "normal" vs. "severe" service intervals
-
Classify driving conditions — Determine if the vehicle qualifies for "severe" service (frequent short trips under 5 miles, extreme temperatures, dusty environments, heavy towing) and adjust intervals accordingly
-
Map fluid service intervals — Schedule oil/filter, transmission fluid, coolant, brake fluid, and power steering fluid changes per OEM mileage and time thresholds
-
Schedule filter replacements — Set intervals for engine air filter (15,000-30,000 mi), cabin air filter (12,000-15,000 mi), and fuel filter per OEM specs
-
Plan inspection checkpoints — At every oil change: inspect belts, hoses, brakes, tires, lights, wipers, and battery; at 30,000-mi intervals: deeper drivetrain inspection
-
Schedule tire maintenance — Rotation every 5,000-7,500 miles, alignment check annually or after impact, balance check with each rotation
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.
- 11d ago First seen · 66 lines · 29 tokens per session scan A b28bc7240b49
design-preventive-maintenance-schedule is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 22d ago), licensed MIT. It adds 29 tokens to every session and 925 once invoked, about $0.0001 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.