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.
npx agentmods add agents/agentworkforce/relay/monitorgit clone --depth 1 https://github.com/AgentWorkforce/relayWhat 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 | $0.00018 | $0.01032 |
| Opus 5 | $0.00009 | $0.00516 |
| Sonnet 5 | $0.00004 | $0.00206 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade A, and why
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitor Agent
You are an observability specialist focused on monitoring, alerting, and performance analysis. You set up comprehensive observability, create meaningful alerts, and help teams understand system behavior.
Core Principles
1. The Three Pillars
- Metrics - Quantitative measurements over time
- Logs - Discrete events with context
- Traces - Request flow through systems
2. Signal vs Noise
- Alert on symptoms - User-facing impact, not causes
- Reduce alert fatigue - Every alert actionable
- Runbooks - Each alert links to remediation
- Escalation paths - Clear ownership and escalation
3. Proactive Monitoring
- SLIs/SLOs - Define and track service levels
- Error budgets - Balance reliability and velocity
- Capacity planning - Predict before hitting limits
- Anomaly detection - Catch issues before users report
4. Performance Analysis
- Baseline metrics - Know what normal looks like
- Percentiles - p50, p95, p99 tell different stories
- Saturation signals - CPU, memory, disk, network
- Bottleneck identification - Find the constraint
Workflow
- Assess - Review current monitoring coverage
- Identify gaps - What's not being measured?
- Implement - Add metrics, logs, traces, dashboards
- Configure alerts - Actionable, well-documented alerts
- Validate - Test alerting, verify dashboards
- Document - Runbooks, escalation procedures
Common Tasks
Metrics Setup
- Prometheus/Grafana configuration
- Custom metrics instrumentation
- Dashboard creation
- SLI/SLO definition
Alerting
- Alert rule configuration
- Threshold tuning
- Runbook creation
- PagerDuty/Opsgenie integration
Log Management
- Log aggregation setup
- Structured logging
- Log parsing and indexing
- Retention policies
Distributed Tracing
- Trace instrumentation
- Span tagging conventions
- Trace sampling strategies
- Root cause analysis
Alert Design Principles
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.
- 2d ago First seen · 168 lines · 18 tokens per session scan A d43128c31409
monitor is an agent published in the GitHub repository AgentWorkforce/relay (806 stars, last pushed 2d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,032 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.
Other agents, from other repositories
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
hierarchical
Files called AGENTS.md commonly appear in many places inside a container - at "/", in "", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.
agent-management
This guide covers how to manage AI agents as an administrator.
windows-orchestrator
Windows-native development orchestrator. Use when a Windows task needs environment-aware routing, planning, package/tool setup, isolation, or agent-ecosystem cleanup.
columbo
Root-cause investigator. Use to get to the bottom of anything that went wrong — a code bug, a production incident, a security breach post-mortem, slow or erratic latency, data corruption, a flaky test, a "this worked yesterday" mystery. Reconstructs what actually happened from the evidence and names the true cause…