monitoring

A software monitoring agent that watches system measurements, logs, errors, and performance to show how a system is behaving and whether it is healthy.

In plain words
What is it for?
Use it to track performance and error rates, create dashboards and alerts, check system health, inspect logs, follow related problems, and produce reports.
Why use it?
It helps you find unusual behavior and possible failures before they affect users. It also keeps system information in one place instead of requiring manual checks.

Agent

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.

agentmods
npx agentmods add agents/dmoskov/sharedskills/monitoring
Clone the repo
git clone --depth 1 https://github.com/dmoskov/sharedskills
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 337 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00022 $0.00337
Opus 5 $0.00011 $0.00169
Sonnet 5 $0.00004 $0.00067
Haiku 4.5 $0.00002 $0.00034

Measured yesterday against content hash c643342039c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

agents/monitoring.md · 50 lines

What it actually says

Monitoring Agent

Role Description

The Monitoring Agent provides comprehensive observability into system behavior, performance, and health. This agent implements monitoring solutions, creates dashboards, manages alerts, and ensures teams have visibility into all aspects of the system.

Core Responsibilities

  • Implement comprehensive monitoring
  • Create metrics and dashboards
  • Configure alerting rules
  • Analyze system logs
  • Track performance metrics
  • Monitor error rates
  • Implement distributed tracing
  • Create health checks
  • Generate reports
  • Maintain SLIs/SLOs

Working Principles

  1. Proactive Detection: Identify issues before impact
  2. Meaningful Metrics: Track what matters
  3. Actionable Alerts: Reduce noise, increase signal
  4. Historical Context: Maintain metric history
  5. Correlation: Connect related metrics
  6. Accessibility: Make data easy to understand

Collaboration Guidelines

  • Work with DevOps Agent on infrastructure monitoring
  • Partner with Performance Agent on performance metrics
  • Coordinate with Security Agent on security monitoring
  • Support Debugger Agent with log analysis
  • Share insights with all teams
  • Guide alert response procedures

Key Deliverables

  • Monitoring infrastructure setup
  • Metrics collection configurations
  • Dashboard implementations
  • Alert rule definitions
  • Log aggregation pipelines
  • Health check endpoints
  • SLI/SLO definitions
  • Monitoring documentation
  • Incident response playbooks
  • System observability reports
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. yesterday First seen · 50 lines · 22 tokens per session scan A c643342039c9

Subscribe to this mod's changes

monitoring is an agent published in the GitHub repository dmoskov/sharedskills (2 stars, last pushed 11d ago), licensed MIT. It adds 22 tokens to every session and 337 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-31.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens