Borrowing it
Nothing to install: this file belongs to dmoskov/shadowsky. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dmoskov/shadowsky/main/.claude/agents/monitoring.mdgit clone --depth 1 https://github.com/dmoskov/shadowskyWrote 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.
[](https://agentmods.dev/agents/dmoskov/shadowsky/monitoring)<a href="https://agentmods.dev/agents/dmoskov/shadowsky/monitoring"><img src="https://agentmods.dev/badge/agents/dmoskov/shadowsky/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.
<a href="https://agentmods.dev/agents/dmoskov/shadowsky/monitoring"><img src="https://agentmods.dev/badge/agents/dmoskov/shadowsky/monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00017 | $0.00353 |
| Opus 5.5 | $0.00007 | $0.00141 |
| Sonnet 5.5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
Monitoring Agent 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.
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
- Proactive Detection: Identify issues before impact
- Meaningful Metrics: Track what matters
- Actionable Alerts: Reduce noise, increase signal
- Historical Context: Maintain metric history
- Correlation: Connect related metrics
- 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
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.
- 1mo ago First seen · 56 lines · 17 tokens per session scan A cc1a695b4b7a
Monitoring Agent is an agent published in the GitHub repository dmoskov/shadowsky (17 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 353 once invoked, about $0.0001 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-01.
Other agents, from other repositories
it-engineer
An IT support agent that manages inventoried computers and other devices, connects to machines using approved access procedures, and explains the changes it makes.
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
aws-principal-architect
Provide expert AWS Principal Architect guidance using AWS Well-Architected Framework principles and AWS best practices.