api-monitor

api-monitor is a skill for Claude Code from ApiliumCode/mayros. It costs 14 tokens per session (232 once invoked), scanned A, original, MIT.

An API-health monitoring skill that checks endpoints and records their status as verifiable assertions. An API is a software interface that lets systems communicate.

In plain words
What is it for?
It helps monitor API availability, track service-level targets, detect incidents, review historical health trends, and record verified down or degraded states.
Why use it?
It keeps current and previous endpoint health in one place and creates tamper-resistant records when an endpoint is degraded or unavailable.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit It helps monitor API availability, track service-level targets, detect incidents, review historical health trends, and record verified down or degraded states.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/apiliumcode/mayros/api-monitor
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 ApiliumCode/mayros --skill api-monitor
Clone the repo
git clone --depth 1 https://github.com/ApiliumCode/mayros

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/apiliumcode/mayros/api-monitor.svg)](https://agentmods.dev/skills/apiliumcode/mayros/api-monitor)
Your own site
<a href="https://agentmods.dev/skills/apiliumcode/mayros/api-monitor"><img src="https://agentmods.dev/badge/skills/apiliumcode/mayros/api-monitor.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 232 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.00014 $0.00232
Opus 5 $0.00007 $0.00116
Sonnet 5 $0.00003 $0.00046
Haiku 4.5 $0.00001 $0.00023

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

Security

Grade A, and why

api-monitor 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 8d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (skill.test.ts, skill.ts, types.ts), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/examples/api-monitor/SKILL.md · 40 lines

What it actually says

api-monitor

Monitor API endpoints and store health status as semantic assertions.

When to Use

Use for API health monitoring, SLA tracking, and incident detection.

Instructions

  1. Recall previous API status from memory
  2. Check endpoint health and assert current status
  3. Use ZK proofs for degraded/down assertions to ensure tamper-proof incident records
  4. Query historical health data for trend analysis
Files

What ships with it

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

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. 8d ago First seen · 40 lines · 14 tokens per session scan A afa1b04610bf

Subscribe to this mod's changes

api-monitor is a skill published in the GitHub repository ApiliumCode/mayros (12 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 232 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-30.