monitoring-setup

monitoring-setup is an agent for Claude Code from navraj007in/architecture-cowork-plugin. It costs 26 tokens per session (5,083 once invoked), scanned A, original, Apache-2.0.

An agent that sets up observability, the systems used to measure, trace, log, and alert on application behavior.

In plain words
What is it for?
It generates metrics, distributed tracing, structured logs, dashboards, alerts, service-level objectives, and runbook templates for application components.
Why use it?
It creates the monitoring pieces needed to find failures, understand performance, and track service health.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is - ./monitoring/prometheus.yml:/etc/prometheus/prometheus.yml.

Part of the architect plugin — 48 skills, 63 commands, 19 agents, 7 MCP servers shipped together

Good fit It generates metrics, distributed tracing, structured logs, dashboards, alerts, service-level objectives, and runbook templates for application components.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/navraj007in/architecture-cowork-plugin
agentmods
npx agentmods add agents/navraj007in/architecture-cowork-plugin/monitoring-setup

Made for: Claude Code.

Or install architect, the plugin that ships this one along with the rest of its 48 skills, 63 commands, 19 agents, 7 MCP servers.

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

agentmods badge for monitoring-setup

README.md
[![agentmods](https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/monitoring-setup/github.svg)](https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/monitoring-setup)
Your own site
<a href="https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/monitoring-setup"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/monitoring-setup/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.

agentmods 80×15 button for monitoring-setup

Your own site · 80×15
<a href="https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/monitoring-setup"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/monitoring-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,083 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00026 $0.05083
Opus 5 $0.00013 $0.02542
Sonnet 5 $0.00005 $0.01017
Haiku 4.5 $0.00003 $0.00508

Measured 10d ago against content hash b70a4429ebe4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

monitoring-setup 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 10d 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.

curl https://dependency-api.example.com/health
agents/monitoring-setup.md · 709 lines

How it starts

The opening of the file, as written. The whole thing — 709 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Monitoring Setup Agent

Autonomous infrastructure agent that configures complete observability pipeline: metrics instrumentation, distributed tracing, structured logging, alert rules, dashboards, SLO definitions, and runbooks.

Input

The /architect:setup-monitoring command passes:

{
  "components": [
    {
      "name": "api-server",
      "type": "backend",
      "language": "typescript",
      "framework": "express",
      "directory": "/path/to/project/api-server",
      "port": 3000
    }
  ],
  "monitoring_config": {
    "metrics_provider": "prometheus",
    "tracing_enabled": true,
    "tracing_provider": "opentelemetry",
    "error_tracking": "sentry",
    "log_aggregation": "loki",
    "alert_severity": "growth"
  },
  "project": {
    "name": "example-app",
    "stage": "growth"
  },
  "tech_stack": {
    "backend": ["Node.js", "Express"],
    "database": "PostgreSQL"
  }
}

Process

Step 1: Detect Existing Instrumentation

For each component, use Glob to check if monitoring code already exists:

  • src/lib/metrics.ts, src/lib/tracing.ts, src/lib/logger.ts (Node.js)
  • src/lib/metrics.py, src/lib/tracing.py, src/lib/logger.py (Python)
  • pkg/metrics.go, pkg/tracing.go, pkg/logger.go (Go)

If files exist, check if they are stubs (empty or placeholder) or fully implemented:

  • Stubs: append missing instrumentation
  • Fully implemented: skip and report "already instrumented"

Step 2: Generate Metrics Instrumentation

Per component and language, generate src/lib/metrics.ts (or equivalent) with:

For Node.js (Express + Prometheus client):

// src/lib/metrics.ts
import promClient from 'prom-client';

// RED method: Rate, Errors, Duration
export const httpRequestDuration = new promClient.Histogram({
  name: 'http_request_duration_seconds',
  help: 'HTTP request latency in seconds',
  labelNames: ['method', 'route', 'status_code'],
  buckets: [0.001, 0.01, 0.05, 0.1, 0.5, 1, 2, 5]
});

export const httpRequestTotal = new promClient.Counter({
  name: 'http_requests_total',
  help: 'Total HTTP requests',
  labelNames: ['method', 'route', 'status_code']
});

export const httpRequestErrors = new promClient.Counter({
  name: 'http_request_errors_total',
  help: 'Total HTTP request errors',
  labelNames: ['method', 'route', 'error_code']
});

// USE method: Utilization, Saturation, Errors (for background workers)
export const dbConnectionPoolActive = new promClient.Gauge({
  name: 'db_connection_pool_active',
  help: 'Active database connections'
});

export const jobQueueLength = new promClient.Gauge({
  name: 'job_queue_length',
  help: 'Number of jobs in queue'
});

// Middleware for auto-instrumentation
export function metricsMiddleware(req, res, next) {
  const startTime = Date.now();
  res.on('finish', () => {
    const duration = (Date.now() - startTime) / 1000;
    const route = req.route?.path || req.url;
    
    httpRequestDuration.labels(req.method, route, res.statusCode).observe(duration);
    httpRequestTotal.labels(req.method, route, res.statusCode).inc();
    
    if (res.statusCode >= 400) {
      httpRequestErrors.labels(req.method, route, res.statusCode).inc();
    }
  });
  next();
}

// Export metrics endpoint
export function registerMetricsEndpoint(app) {
  app.get('/metrics', async (req, res) => {
    res.set('Content-Type', promClient.register.contentType);
    res.end(await promClient.register.metrics());
  });
}

Read the full file on GitHub · 709 lines

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. 10d ago First seen · 709 lines · 26 tokens per session scan A b70a4429ebe4

Subscribe to this mod's changes

monitoring-setup is an agent published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 5,083 once invoked, about $0.0001 per session on Opus 5. 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-31.

Related

Other agents, from other repositories

section-writer

Generates self-contained implementation section content. Outputs raw markdown. Used by /deep-plan for parallel section generation.

piercelamb/deep-plan · 26 tokens

opus-plan-reviewer

Reviews implementation plans (fallback when external LLMs unavailable).

piercelamb/deep-plan · 17 tokens

spec-scanner

Scans a codebase using LLM-driven heuristics to detect framework, patterns, entities, and registration points. Produces a persistent project profile that other agents read for wiring-aware implementation.

Habib0x0/spec-driven-plugin · 41 tokens

spec-documenter

Generates user-facing documentation from spec files and implemented code. Produces API references, user guides, and architecture decision records. Context: Feature implementation is complete and user needs documentation. user: "/spec-docs" assistant: "I'll generate documentation from the spec and implementation." The…

Habib0x0/spec-driven-plugin · 100 tokens

spec-validator

Use this agent when you need to validate a spec for completeness, consistency, and implementation readiness. Examples: Context: User has finished creating a spec and wants to verify it's ready for implementation. user: "I've finished the spec for user-authentication. Can you validate it?" assistant: "I'll use the…

Habib0x0/spec-driven-plugin · 275 tokens

spec-consultant

Domain expert consultant that provides focused analysis on a specific topic during brainstorming. This is a parameterized agent — the spawning command passes the expert role, domain expertise, discussion context, and specific question via the prompt. Returns structured analysis to the Lead. Context: During…

Habib0x0/spec-driven-plugin · 228 tokens