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 LGDiMaggio/claude-stwinbox-diagnostics --skill operator-diagnostic-reportgit clone --depth 1 https://github.com/LGDiMaggio/claude-stwinbox-diagnosticsWrote 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/lgdimaggio/claude-stwinbox-diagnostics/operator-diagnostic-report)<a href="https://agentmods.dev/skills/lgdimaggio/claude-stwinbox-diagnostics/operator-diagnostic-report"><img src="https://agentmods.dev/badge/skills/lgdimaggio/claude-stwinbox-diagnostics/operator-diagnostic-report/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/lgdimaggio/claude-stwinbox-diagnostics/operator-diagnostic-report"><img src="https://agentmods.dev/badge/skills/lgdimaggio/claude-stwinbox-diagnostics/operator-diagnostic-report.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.00102 | $0.02658 |
| Opus 5 | $0.00051 | $0.01329 |
| Sonnet 5 | $0.00020 | $0.00532 |
| Haiku 4.5 | $0.00010 | $0.00266 |
Grade A, and why
operator-diagnostic-report 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operator Diagnostic Report
You are generating diagnostic reports for maintenance teams and machine operators. Reports must be clear, actionable, and accessible to people who may not have vibration analysis expertise.
⛔ Data Integrity Rules — MANDATORY
These rules override everything else. Violating them produces a misleading report.
NEVER invent metadata the user has not provided
- Machine name: Use the value the user stated. If unknown → write "Not specified".
- Machine location: Use the value the user stated. If unknown → write "Not specified".
- Operator / analyst name: Use the value the user stated. If unknown → omit the field.
- RPM / shaft speed: Use the value the user stated or the value returned by
diagnose_vibration. If unknown → write "Unknown — not provided by operator". - Bearing type: Only include if the user provided a bearing designation or geometry.
Do NOT fill template placeholders ({machine_location}, {machine_name}, etc.)
with guessed or hallucinated values. If a placeholder has no data, replace it
with "Not specified" or remove the row entirely.
NEVER present hypotheses as confirmed findings
If diagnose_vibration was called without RPM, the tool cannot identify
shaft-frequency faults (unbalance, misalignment, looseness). The report must:
- State clearly: "Shaft speed was not provided; shaft-frequency analysis was not performed."
- Report only the data the tool actually returned (RMS, kurtosis, crest factor, ISO severity, spectral peaks).
- NOT add fault diagnoses that the tool did not produce (e.g. do not write "possible unbalance" if the tool never returned an unbalance diagnosis).
If bearing data was not provided, do NOT add bearing fault hypotheses.
Distinguish MCP tool output from general knowledge
When including information based on your general engineering knowledge (e.g. typical RPM ranges, ISO 1940 balancing grades, common maintenance procedures) rather than MCP tool output, you MUST clearly label it:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 277 lines · 102 tokens per session scan A 9cfeba5e8efc
operator-diagnostic-report is a skill published in the GitHub repository LGDiMaggio/claude-stwinbox-diagnostics (8 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 102 tokens to every session and 2,658 once invoked, about $0.0005 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
bearing-diagnosis
Complete bearing fault diagnostic workflow using vibration analysis and the predictive-maintenance-mcp server. Use this skill when the user says "diagnose bearing", "bearing fault", "bearing check", "detect bearing damage", "bearing vibration analysis", "inner race fault", "outer race fault", "ball defect", "cage…
prognostics
Prognostic assessment workflow: trend analysis, degradation onset detection, and Remaining Useful Life (RUL) estimation using the predictive-maintenance-mcp server. Use this skill when the user says "trend analysis", "degradation trend", "RUL", "remaining useful life", "prognosis", "prognostics", "failure prediction"…
signal-management
Signal loading, generation, and cache management using the predictive-maintenance-mcp server. Use this skill when the user says "load signal", "import signal", "list signals", "available signals", "generate test signal", "create test data", "synthetic signal", "clear cache", "signal info", "what signals are loaded"…
report-generation
Generate professional diagnostic reports (HTML, DOCX) for vibration analysis using the predictive-maintenance-mcp server. Use this skill when the user says "generate report", "create report", "export report", "diagnostic report", "save analysis", "create PDF", "archive results", "full documentation", "DOCX report"…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.