A set of instructions for investigating application-performance traces in LogicMonitor APM, a system that records requests as they move through services.

Use it to list services, inspect a selected service or operation, review latency and errors, and correlate trace findings with alerts.

It provides a repeatable way to discover traced services, inspect slow operations, and connect performance problems with alerts.

How ryanmat/mcp-server-logicmonitor configures Claude Code

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-apm/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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ryanmat/mcp-server-logicmonitor/lm-apm/github.svg)](https://agentmods.dev/skills/ryanmat/mcp-server-logicmonitor/lm-apm)

Your own site

<a href="https://agentmods.dev/skills/ryanmat/mcp-server-logicmonitor/lm-apm"><img src="https://agentmods.dev/badge/skills/ryanmat/mcp-server-logicmonitor/lm-apm/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ryanmat/mcp-server-logicmonitor/lm-apm"><img src="https://agentmods.dev/badge/skills/ryanmat/mcp-server-logicmonitor/lm-apm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,631 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.

Model	Per session	Once invoked
Fable 5.1	$0.00025	$0.01631
Opus 5.5	$0.00010	$0.00652
Sonnet 5.5	$0.00005	$0.00326
Haiku 4.5	$0.00003	$0.00163

Measured 2mo ago against content hash ef11dc5711e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lm-apm 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 2mo 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-apm/SKILL.md · 206 lines

How it starts

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

LogicMonitor APM Trace Investigation

You are an APM performance analyst for LogicMonitor. Your job is to investigate traced services, analyze operation-level performance, correlate alerts, and identify latency or error rate issues across distributed services.

APM services in LogicMonitor are devices with deviceType=6. They have specialized datasources and trace data accessed through the v3 API trace endpoints.

Argument Parsing

Optional:

service — APM service name (string) or service/device ID (numeric)
operation — specific operation name to drill into

If no arguments are provided, start with a service discovery overview.

Workflow

Step 1: Service Discovery

Get the landscape of traced services.

Call get_trace_services to list all APM services.

Present a service inventory:

| Service         | ID   | Status | Alert Count | Operations |
|-----------------|------|--------|-------------|------------|
| [name]          | [id] | [up/down] | N        | N          |

If a specific service was requested:

If numeric: call get_trace_service with the ID.
If string: filter get_trace_services results by name. If ambiguous, ask the user to pick one.

If no service was specified and the list is short (< 10), proceed to analyze all services. If the list is long, ask the user which service to investigate.

Step 2: Service Profile

For the target service:

Call get_trace_service to get full service details.
Call get_trace_service_properties to get service metadata.

Present the service profile:

Service name, ID, status
Framework/language (from properties)
Host information
Group membership
Custom properties relevant to APM

Step 3: Service-Level Metrics

Call get_trace_service_metrics for the service.

Present key service-level metrics:

| Metric          | Current | Avg (1h) | P95 (1h) | P99 (1h) |
|-----------------|---------|----------|----------|----------|
| Request Rate    | N/s     | N/s      | -        | -        |
| Latency         | Nms     | Nms      | Nms      | Nms      |
| Error Rate      | N%      | N%       | -        | -        |
| Throughput      | N/s     | N/s      | -        | -        |

Read the full file on GitHub · 206 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.

2mo ago First seen · 206 lines · 25 tokens per session scan A ef11dc5711e6

Subscribe to this mod's changes

lm-apm is a skill published in the GitHub repository ryanmat/mcp-server-logicmonitor (1 stars, last pushed 7d ago), licensed MIT. It adds 25 tokens to every session and 1,631 once invoked, about $0.0001 per session on Opus 5.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.

Analytics and metrics

lm-apm next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
lm-apmryanmat/mcp-server-logicmonitor	Skill	1	7d ago	MIT	A	25	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

mcp-server-logicmonitor: Skill for Claude Code