create-monitoring

create-monitoring is a command for Claude Code from jeremylongshore/plugins-nixtla. It costs 4 tokens per session (16,117 once invoked), scanned C, original, no licence file.

A command for creating a dashboard that monitors APIs. The available description does not specify which services, metrics, or alerting options it supports.

In plain words
What is it for?
Use it when you need to create an API monitoring dashboard.
Why use it?
It can provide a central place to view API monitoring information, but the input does not give enough detail to describe more.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the api-monitoring-dashboard plugin — 1 command shipped together

Good fit Use it when you need to create an API monitoring dashboard.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/jeremylongshore/plugins-nixtla/create-monitoring
Install

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.

Clone the repo
git clone --depth 1 https://github.com/jeremylongshore/plugins-nixtla

Made for: Claude Code.

Or install api-monitoring-dashboard, the plugin that ships this one along with the rest of its 1 command.

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 create-monitoring

README.md
[![agentmods](https://agentmods.dev/badge/commands/jeremylongshore/plugins-nixtla/create-monitoring/github.svg)](https://agentmods.dev/commands/jeremylongshore/plugins-nixtla/create-monitoring)
Your own site
<a href="https://agentmods.dev/commands/jeremylongshore/plugins-nixtla/create-monitoring"><img src="https://agentmods.dev/badge/commands/jeremylongshore/plugins-nixtla/create-monitoring/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 create-monitoring

Your own site · 80×15
<a href="https://agentmods.dev/commands/jeremylongshore/plugins-nixtla/create-monitoring"><img src="https://agentmods.dev/badge/commands/jeremylongshore/plugins-nixtla/create-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 16,117 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown 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.00004 $0.16117
Opus 5 $0.00002 $0.08058
Sonnet 5 $0.00001 $0.03223
Haiku 4.5 $0.00000 $0.01612

Measured 7d ago against content hash fe559bd3ab97, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade C, and why

create-monitoring scanned grade C with 2 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 7d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

| "Error reading Prometheus" | Corrupt WAL (write-ahead log) | Delete WAL directory: `rm -rf /prometheus/wal/*` and restart |

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

response = requests.get(endpoint, timeout=5)
010-archive/backups-20251108/plugin-enhancements/plugin-backups/api-monitoring-dashboard_20251019_200630/commands/create-monitoring.md · 2,182 lines

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.

Read it on GitHub

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. 7d ago First seen · 2,182 lines · 4 tokens per session scan C fe559bd3ab97

Subscribe to this mod's changes

create-monitoring is a command published in the GitHub repository jeremylongshore/plugins-nixtla (11 stars, last pushed 3d ago), with no licence file. It adds 4 tokens to every session and 16,117 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.