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.
git clone --depth 1 https://github.com/LGDiMaggio/predictive-maintenance-mcpWrote 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/agents/lgdimaggio/predictive-maintenance-mcp/diagnostic-pipeline)<a href="https://agentmods.dev/agents/lgdimaggio/predictive-maintenance-mcp/diagnostic-pipeline"><img src="https://agentmods.dev/badge/agents/lgdimaggio/predictive-maintenance-mcp/diagnostic-pipeline/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/agents/lgdimaggio/predictive-maintenance-mcp/diagnostic-pipeline"><img src="https://agentmods.dev/badge/agents/lgdimaggio/predictive-maintenance-mcp/diagnostic-pipeline.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.00016 | $0.01628 |
| Opus 5 | $0.00008 | $0.00814 |
| Sonnet 5 | $0.00003 | $0.00326 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
Diagnostic Pipeline 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 143 lines · 16 tokens per session scan A 9f61cd37d88f
Diagnostic Pipeline is an agent published in the GitHub repository LGDiMaggio/predictive-maintenance-mcp (83 stars, last pushed 20d ago), with no licence file. It adds 16 tokens to every session and 1,628 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-30.
Other agents, from other repositories
perf
Performance audit for web applications. Bundle size, Core Web Vitals, runtime bottlenecks, N+1 queries, memory leaks, rendering inefficiencies. Framework-aware (Next.js, Vite, Webpack). Use before deploys or when things feel slow.
feasibility-check
Pre-build feasibility checker. Use when you have a spec, plan, or requirements doc and want to confirm the codebase can support it before writing code. Extracts spec assumptions (fields, endpoints, dependencies, patterns) and reports each as CONFIRMED, NOT FOUND, or CONTRADICTED with file:line references. Read-only.
performance-analyzer
MUST BE USED for code performance issues. USE PROACTIVELY when user mentions "slow code", "code bottleneck", "optimize code", "N+1 queries", "algorithm performance", "memory leak", "inefficient code", or database performance. Identifies algorithmic issues, database problems, memory leaks, and code optimization…
usage-finder
MUST BE USED for finding code usages and building usage maps. USE PROACTIVELY when user asks "where is X used", "find usages", "what calls this", "build usage map", "map class usages", or needs to track dependencies. Expert at finding functions, methods, classes, variables across codebases and generating structured…
dependency-analyzer
MUST BE USED for dependency analysis. USE PROACTIVELY when user asks about "dependencies", "circular deps", "security vulnerabilities", "bundle size", "npm audit", or package issues. Supports npm, pip, go modules, maven, cargo, composer.
code-analyst
MUST BE USED for code file analysis. Performs deep analysis of architecture, patterns, dependencies, complexity, issues, and recommendations. USE PROACTIVELY when user asks to analyze, understand, review, investigate, rework, improve, or check any code file, module, README, or documentation.