Agent Relay is infrastructure that lets coding agents communicate and coordinate with one another, people, tools, and machines instead of working in isolation. Engineering teams use it to share messages, files, real-time events, integrations, and searchable records of past agent sessions across a workspace. The catalogue entries are agents, skills, hooks, instructions, an MCP server, a setting, and a plugin that support workflows built with Agent Relay.
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.
git clone --depth 1 https://github.com/AgentWorkforce/relayWrote 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/agentworkforce/relay/monitor)<a href="https://agentmods.dev/agents/agentworkforce/relay/monitor"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/monitor/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/agentworkforce/relay/monitor"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/monitor.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.00018 | $0.01032 |
| Opus 5.5 | $0.00007 | $0.00413 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 168 lines · 18 tokens per session scan A d43128c31409
monitor is an agent published in the GitHub repository AgentWorkforce/relay (1,042 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 1,032 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-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…
developer
Implements exactly one story from docs/stories/, test-first. Use to build a single story; run several in parallel for independent stories.
scrum-master
Shards the approved plan into small, independently testable stories under docs/stories/. Use once the owner has approved the plan.
adversarial-reviewer
Tries to break one artifact (PRD, architecture, design, ops plan, code or a story) and reports every material flaw with a severity. Use before approving any artifact.
designer
Owns docs/ux-spec.md and docs/mockup.html. Use for user flows, screens and a working HTML mockup.