monitoring-observability

monitoring-observability is a skill for Codex from san-npm/skills-ws. It costs 78 tokens per session (731 once invoked), scanned A, original, MIT.

A reference guide for watching running software through logs, measurements, traces, dashboards, service targets, and incident procedures.

In plain words
What is it for?
Use it when adding monitoring to a service, creating metrics and alerts, setting reliability targets, connecting traces to logs, or handling an incident.
Why use it?
It helps teams understand what is happening in production and investigate failures or slowdowns using consistent signals and response steps.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it when adding monitoring to a service, creating metrics and alerts, setting reliability targets, connecting traces to logs, or handling an incident.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/san-npm/skills-ws/monitoring-observability
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 san-npm/skills-ws --skill monitoring-observability
Clone the repo
git clone --depth 1 https://github.com/san-npm/skills-ws

Made for: 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 monitoring-observability

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/san-npm/skills-ws/monitoring-observability"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/monitoring-observability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 731 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.00078 $0.00731
Opus 5.5 $0.00031 $0.00292
Sonnet 5.5 $0.00016 $0.00146
Haiku 4.5 $0.00008 $0.00073

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

Security

Grade A, and why

monitoring-observability 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.

skills/monitoring-observability/SKILL.md · 34 lines

How it starts

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

Monitoring & Observability

Reference guide

Read only the references needed for the current request:

Read the full file on GitHub · 34 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. 2mo ago First seen · 34 lines · 78 tokens per session scan A a99533605bb6

Subscribe to this mod's changes

monitoring-observability is a skill published in the GitHub repository san-npm/skills-ws (4 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 731 once invoked, about $0.0003 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.

Related

monitoring-observability compared with skills from other repositories

monitoring-observability next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
monitoring-observabilitysan-npm/skills-wsSkill41mo agoMITA78Codex
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code