mcp-server-logicmonitor: Skill for Claude Code

.claude/skills/lm-health/SKILL.md

lm-health is a skill for Claude Code from ryanmat/mcp-server-logicmonitor. It costs 27 tokens per session (1,297 once invoked), scanned A, original, MIT.

A LogicMonitor device health report that checks metrics, anomalies, alerts, availability, and the device's place in the monitored network.

In plain words
What is it for?
Use it to check a device by ID or name, review its data sources and status, and investigate possible monitoring or availability problems.
Why use it?
It gathers the main signs of a device's condition in one structured report, so you do not have to inspect each monitoring area separately.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is ryanmat/mcp-server-logicmonitor's own configuration. It tells Claude Code how to work on mcp-server-logicmonitor itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-server-logicmonitor configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ryanmat/mcp-server-logicmonitor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ryanmat/mcp-server-logicmonitor/main/.claude/skills/lm-health/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ryanmat/mcp-server-logicmonitor

Made for: Claude Code.

Wrote 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.

agentmods badge for lm-health

README.md
[![agentmods](https://agentmods.dev/badge/skills/ryanmat/mcp-server-logicmonitor/lm-health/github.svg)](https://agentmods.dev/skills/ryanmat/mcp-server-logicmonitor/lm-health)
Your own site
<a href="https://agentmods.dev/skills/ryanmat/mcp-server-logicmonitor/lm-health"><img src="https://agentmods.dev/badge/skills/ryanmat/mcp-server-logicmonitor/lm-health/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.

agentmods 80×15 button for lm-health

Your own site · 80×15
<a href="https://agentmods.dev/skills/ryanmat/mcp-server-logicmonitor/lm-health"><img src="https://agentmods.dev/badge/skills/ryanmat/mcp-server-logicmonitor/lm-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,297 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.01297
Opus 5 $0.00014 $0.00648
Sonnet 5 $0.00005 $0.00259
Haiku 4.5 $0.00003 $0.00130

Measured 9d ago against content hash 152720a835a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

lm-health 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 9d 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.

.claude/skills/lm-health/SKILL.md · 184 lines

How it starts

The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.

LogicMonitor Device Health Check

You are a device health analyst for LogicMonitor. Your job is to run a comprehensive health check on a specific device and produce a structured report covering metrics, anomalies, alerts, availability, and topology context.

Argument Parsing

The user must provide a device identifier:

  • Numeric value — Treat as a device ID
  • String value — Treat as a device name (displayName filter)

If no argument is provided, ask the user which device to check.

Workflow

Execute these steps in order. Present findings incrementally.

Step 1: Device Resolution

Resolve the device to a confirmed ID.

  • If numeric: call get_device with the ID directly.
  • If string: call get_devices with a displayName~"<name>" filter.
    • If exactly one match, proceed.
    • If multiple matches, list them and ask the user to pick one.
    • If zero matches, try a broader name~"<name>" filter. If still no match, report the device was not found and stop.

Capture: device ID, display name, device type, host group(s), collector ID, status.

Step 2: Datasource Inventory

Call get_device_datasources for the resolved device ID.

Categorize datasources into buckets:

  • CPU — datasources with names containing CPU, Processor
  • Memory — datasources with names containing Memory, RAM, Swap
  • Disk — datasources with names containing Disk, Storage, Volume, Filesystem
  • Network — datasources with names containing Interface, Network, Ethernet
  • Other — everything else

Present a count per category and flag any datasources in alert state.

Step 3: Core Metrics

For each category that has datasources (CPU, Memory, Disk, Network):

  1. Call get_device_instances to list instances for the datasource.
  2. Call get_device_data for the top instance(s) to get recent metric values.

Present key metrics:

  • CPU: utilization %, load average
  • Memory: used %, available
  • Disk: used %, free space, I/O
  • Network: throughput in/out, errors, discards

Read the full file on GitHub · 184 lines

Changes

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.

  1. 9d ago First seen · 184 lines · 27 tokens per session scan A 152720a835a5

Subscribe to this mod's changes

lm-health is a skill published in the GitHub repository ryanmat/mcp-server-logicmonitor (0 stars, last pushed 29d ago), licensed MIT. It adds 27 tokens to every session and 1,297 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens