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 commands/evan043/claude-cli-advanced-starter-pack/monitoring-setup.templategit clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/commands/evan043/claude-cli-advanced-starter-pack/monitoring-setup.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/monitoring-setup.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/monitoring-setup.template.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.03698 |
| Opus 5 | $0.00000 | $0.01849 |
| Sonnet 5 | $0.00000 | $0.00740 |
| Haiku 4.5 | $0.00000 | $0.00370 |
Grade A, and why
monitoring-setup.template scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. Provide curl commands to manually test health endpoints How it starts
The opening of the file, as written. The whole thing — 697 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
monitoring-setup — Codex Runtime
This command configures monitoring for your deployed services. Railway MCP is unavailable in Codex.
What I Can Do
- Generate monitoring configuration files (uptime checks, alert rules)
- Show you the Railway CLI commands to set up monitoring
- Provide curl commands to manually test health endpoints
Manual Railway Monitoring Setup
# Install Railway CLI if needed
npm install -g @railway/cli
railway login
# List your services
railway status
# Set up environment variables for monitoring
railway variables set MONITORING_ENABLED=true
Alternative: Uptime Monitors
I can generate configuration for third-party monitors (UptimeRobot, BetterUptime, etc.) that work without Railway MCP. Just tell me your service URLs.
For full Railway MCP monitoring setup, use Claude Code CLI: /monitoring-setup
description: Set up monitoring and observability for your application type: project complexity: medium allowed-tools: Bash, Read, Write, Grep, Glob category: devops
/monitoring-setup
Set up comprehensive monitoring, error tracking, and observability for your application.
Usage
/monitoring-setup
/monitoring-setup --error-tracking
/monitoring-setup --apm
/monitoring-setup --logs
What It Does
- Error Tracking - Set up Sentry or similar
- Application Performance Monitoring - APM integration
- Log Aggregation - Structured logging setup
- Health Checks - Endpoint creation
- Alerting - Configure notifications
- Dashboards - Monitoring dashboard setup
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.
- 5d ago First seen · 697 lines · 0 tokens per session scan A 2c37b985fbd5
monitoring-setup.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,698 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
account
This API allows you to manage your Scaleway Projects.
index
This documentation covers all available Dashmate CLI commands, their parameters, and behavior.
deploy
Build, test, deploy with staged rollout.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
/forge:integrate is the integration assistant for connecting your project to external services. It covers version control (GitHub, GitLab), monitoring (Sentry, Datadog), communication (Slack, Discord), databases (PostgreSQL, Redis, MongoDB), and cloud platforms (AWS, GCP, Vercel, Netlify). For each service, it checks…
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.