api-monitoring

api-monitoring is a skill for Claude Code from Postman-Devrel/postman-claude-code-plugin. It costs 131 tokens per session (1,923 once invoked), scanned A, original, Apache-2.0.

A tool for creating and managing Postman Monitors, which are scheduled checks against a live web API. It can also run checks on demand and inspect their history, including through a runner inside a private network.

In plain words
What is it for?
Use it to create, schedule, pause, resume, run, and inspect recurring API checks and their results.
Why use it?
It catches API failures over time and helps investigate when a scheduled check fails, including when the API cannot be reached directly from the cloud.

Skill for Claude Code

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

Part of the postman plugin — 13 skills, 1 hook, 1 MCP server shipped together

Good fit Use it to create, schedule, pause, resume, run, and inspect recurring API checks and their results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/postman-devrel/postman-claude-code-plugin/api-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.

Any agent
npx skills add Postman-Devrel/postman-claude-code-plugin --skill api-monitoring
Clone the repo
git clone --depth 1 https://github.com/Postman-Devrel/postman-claude-code-plugin

Made for: Claude Code.

Or install postman, the plugin that ships this one along with the rest of its 13 skills, 1 hook, 1 MCP server.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/postman-devrel/postman-claude-code-plugin/api-monitoring/github.svg)](https://agentmods.dev/skills/postman-devrel/postman-claude-code-plugin/api-monitoring)
Your own site
<a href="https://agentmods.dev/skills/postman-devrel/postman-claude-code-plugin/api-monitoring"><img src="https://agentmods.dev/badge/skills/postman-devrel/postman-claude-code-plugin/api-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 api-monitoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/postman-devrel/postman-claude-code-plugin/api-monitoring"><img src="https://agentmods.dev/badge/skills/postman-devrel/postman-claude-code-plugin/api-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 131 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,923 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.00131 $0.01923
Opus 5.5 $0.00052 $0.00769
Sonnet 5.5 $0.00026 $0.00385
Haiku 4.5 $0.00013 $0.00192

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

Security

Grade A, and why

api-monitoring 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 1mo 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.

skills/api-monitoring/SKILL.md · 137 lines

How it starts

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

API Monitoring

Overview

A Monitor is a recurring, scheduled check against a live API. The CLI now owns its full lifecycle: monitor create/update/delete/pause/resume manage the schedule and configuration, monitor list/get discover and inspect existing ones, monitor run triggers an ad hoc run, and monitor jobs/monitor runs inspect what actually happened during a run. There is no remaining task here that has to go through the Postman app.

postman runner is a separate, infrastructure-level concern: it starts a self-hosted execution agent so Monitor runs can reach APIs that live behind a private network Postman's cloud can't reach directly, and it lists the values (Postman regions or self-hosted runner ids) that monitor create/update --runner accepts.

Creating and scheduling a monitor

monitor create -c <collectionId> is the minimum — name defaults to the linked collection's own name. Workspace comes from -w, or falls back to the workspace named in the local .postman/resources.yaml manifest; without either, creation fails. --schedule <cron> plus --timezone (defaults to the host machine's zone) set when it fires; --runner (repeatable) says where from — a Postman region name (postman runner regions) or a self-hosted runner's id (postman runner list), and both can be mixed in the same monitor. --notify-email (repeatable) and --notification-limit control failure alerts. The run itself is shaped by the same options as a collection run — --retry (service caps at 2), --timeout, --delay, --strict-ssl/--insecure, --follow-redirects/--block-redirects, and dataset iteration via --dataset-id/--dataset-view-id/--iteration-count/ --iteration-strategy. Creation triggers an immediate run by default; pass --no-run-now to skip that.

Updating, pausing, and deleting

monitor update <monitorId> takes the same schedule/runner/notification/ run-option flags as create, plus --clear-notifications to wipe every recipient. It cannot change the linked collection or environment — delete and recreate the monitor instead — and it does not pause or resume; use monitor pause/monitor resume for that. monitor delete <monitorId> prompts for confirmation unless -y/--yes is passed, and is permanent.

Read the full file on GitHub · 137 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. 1mo ago First seen · 137 lines · 131 tokens per session scan A c1f4b6f1194f

Subscribe to this mod's changes

api-monitoring is a skill published in the GitHub repository Postman-Devrel/postman-claude-code-plugin (41 stars, last pushed 21d ago), licensed Apache-2.0. It adds 131 tokens to every session and 1,923 once invoked, about $0.0005 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-09-20.

Related

Other skills, from other repositories

postman

Full API lifecycle management through Postman. Sync OpenAPI specs to collections, generate typed client code, run API tests, create mock servers, publish documentation, audit security against OWASP Top 10, and discover APIs across workspaces. Requires the Postman MCP Server. Use this skill when the user mentions…

Postman-Devrel/agent-skills · 111 tokens

postman-api-readiness

Analyze any API for AI agent compatibility. Scans OpenAPI specs across 8 pillars (48 checks), scores agent-readiness 0-100, and provides prioritized fix recommendations. Use this skill when the user asks: "Is my API agent-ready?", "Scan my API", "Analyze my OpenAPI spec", "What's wrong with my API for AI agents?"…

Postman-Devrel/agent-skills · 108 tokens

stripe-projects

Provision SaaS services + sync creds via Stripe Projects.

NousResearch/hermes-agent · 15 tokens

django-storages-s3

Use when configuring Django to store static and media files on AWS S3 with django-storages. Invoke when working with the STORAGES setting, S3 buckets, presigned URLs, CloudFront, or boto3-backed file storage in settings.py. Configures the Django 4.2+ STORAGES dict, public/private custom backends, presigned GET/POST…

Jeffallan/claude-skills · 138 tokens

websocket-engineer

Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.

Jeffallan/claude-skills · 36 tokens

azure-eventhub-dotnet

Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: "Event Hubs", "event streaming"…

microsoft/skills · 94 tokens