mainframe-self-monitoring

mainframe-self-monitoring is a skill for Claude Code, Codex from CATWILLgh/MAINFRAME. It costs 55 tokens per session (620 once invoked), scanned A, original, MIT.

A method for building an application's own system or diagnostics page with service health, resource metrics, logs, and optional scoped container controls or data previews.

In plain words
What is it for?
Use it to design, implement, or repair embedded health checks, metrics, logs, resource views, and carefully authorized diagnostic actions.
Why use it?
It helps make operational information useful and avoids treating an application's embedded page as a replacement for external monitoring.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to design, implement, or repair embedded health checks, metrics, logs, resource views, and carefully authorized diagnostic actions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/catwillgh/mainframe/mainframe-self-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 CATWILLgh/MAINFRAME --skill mainframe-self-monitoring
Clone the repo
git clone --depth 1 https://github.com/CATWILLgh/MAINFRAME

Made for: Claude Code, Codex.

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 mainframe-self-monitoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/catwillgh/mainframe/mainframe-self-monitoring/github.svg)](https://agentmods.dev/skills/catwillgh/mainframe/mainframe-self-monitoring)
Your own site
<a href="https://agentmods.dev/skills/catwillgh/mainframe/mainframe-self-monitoring"><img src="https://agentmods.dev/badge/skills/catwillgh/mainframe/mainframe-self-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 mainframe-self-monitoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/catwillgh/mainframe/mainframe-self-monitoring"><img src="https://agentmods.dev/badge/skills/catwillgh/mainframe/mainframe-self-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 620 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.00055 $0.00620
Opus 5.5 $0.00022 $0.00248
Sonnet 5.5 $0.00011 $0.00124
Haiku 4.5 $0.00006 $0.00062

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

Security

Grade A, and why

mainframe-self-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 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.

skills/mainframe-self-monitoring/SKILL.md · 58 lines

How it starts

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

Embedded system diagnostics

Build a useful operator view in the receiving application's stack and design system. Start with observation; add container mutations and data browsing only where the requested product needs them and their separate permissions are defined. Do not automatically install Docker access, database explorers, a metrics platform or a different frontend/backend framework. This method is not a replacement for external monitoring: a failed application cannot reliably report its own outage.

Inspect existing health checks, telemetry, identities, tenants, resource ownership, deployment and operator workflows. Establish the exact target environment and which users may see each class of information. Reuse current instrumentation, clients and authorization. Development authority does not grant permission to restart production resources, delete images, browse unrelated data or expose a privileged daemon socket.

Read for the current decision

  • Signals: bounded collection, health semantics, freshness, units, missing data and failure isolation.
  • Docker and Compose: optional runtime adapter, actual target identity, scope enforcement, actions and configuration display.
  • Data previews: optional PostgreSQL, Redis and Kafka inspection with explicit cost, disclosure and access boundaries.
  • Interface and verification: operator journey, truthful actions, tests and actual UI/runtime acceptance.

Use the relevant backend/frontend engineering method and mainframe-testing for implementation checks. Use mainframe-infrastructure for actual platform access or changes, mainframe-k3s for Kubernetes operations and mainframe-clickhouse for that database's query safety. Use mainframe-notifications only if this work also requires event-driven outbound alerts.

Complete the slice

Define a small typed server contract for each enabled capability: authorized resource identity, observation time, freshness, status, optional value/unit and safe error. Enforce authorization and resource scope server-side for every request, including direct IDs and background jobs. UI visibility is not a guard. Separate metadata, logs/data and mutations; an authenticated account is not sufficient permission for host-wide information.

Read the full file on GitHub · 58 lines

Files

What ships with it

4 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. 9d ago First seen · 58 lines · 55 tokens per session scan A 82a0dd2767b4

Subscribe to this mod's changes

mainframe-self-monitoring is a skill published in the GitHub repository CATWILLgh/MAINFRAME (2 stars, last pushed 3d ago), licensed MIT. It adds 55 tokens to every session and 620 once invoked, about $0.0002 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-10-07.