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 skills/agentfront/frontmcp/frontmcp-observabilitynpx skills add agentfront/frontmcp --skill frontmcp-observabilitygit clone --depth 1 https://github.com/agentfront/frontmcpWrote 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/skills/agentfront/frontmcp/frontmcp-observability)<a href="https://agentmods.dev/skills/agentfront/frontmcp/frontmcp-observability"><img src="https://agentmods.dev/badge/skills/agentfront/frontmcp/frontmcp-observability.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.00177 | $0.03110 |
| Opus 5 | $0.00088 | $0.01555 |
| Sonnet 5 | $0.00035 | $0.00622 |
| Haiku 4.5 | $0.00018 | $0.00311 |
Grade A, and why
frontmcp-observability 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 4d 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.
| [`enable-metrics-endpoint`](./examples/metrics-endpoint/enable-metrics-endpoint.md) | Basic | Turn on the /metrics endpoint with defaults and scrape it with curl. | How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FrontMCP Observability
Router for adding observability to FrontMCP servers. Covers distributed tracing (OpenTelemetry), structured JSON logging, per-request log collection, the this.telemetry developer API, and vendor integrations.
When to Use This Skill
Must Use
- Adding tracing, logging, or monitoring to a FrontMCP server
- Connecting Coralogix, Datadog, Logz.io, Grafana, or any OTLP backend
- Using
this.telemetryto create custom spans in tools, plugins, or agents - Setting up structured logging with winston, pino, or NDJSON stdout
- Testing that spans and log entries are created correctly
Recommended
- Before going to production (see also
frontmcp-production-readiness) - When debugging request latency or error rates
- When building plugins that need trace context propagation
Skip When
- Building a prototype that doesn't need observability yet
- Configuring auth, transport, or throttle (see
frontmcp-config) - Setting up the project from scratch (see
frontmcp-setup)
Decision: Use this skill when you need to observe, trace, or log your server. Start with
tracing-setupfor auto-instrumentation, addstructured-loggingfor production logs, and usetelemetry-apifor custom spans in your code.
Prerequisites
- A working FrontMCP server (see
frontmcp-setup) npm install @frontmcp/observability
Step 1: Choose What You Need
| I want to... | Reference |
|---|---|
| Enable auto-tracing for all flows | references/tracing-setup.md |
| Add structured JSON logging with trace correlation | references/structured-logging.md |
| Create custom spans in tools/plugins | references/telemetry-api.md |
| Connect Coralogix, Datadog, Logz.io, Grafana | references/vendor-integrations.md |
| Test that spans and logs are correct | references/testing-observability.md |
Expose Prometheus /metrics endpoint |
references/metrics-endpoint.md |
What ships with it
18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/metrics-endpoint/enable-metrics-endpoint.md 2.4 KB
- examples/structured-logging/stdout-logging.md 1.8 KB
- examples/structured-logging/winston-integration.md 2.0 KB
- examples/telemetry-api/agent-nested-tracing.md 2.7 KB
- examples/telemetry-api/plugin-telemetry.md 2.7 KB
- examples/telemetry-api/skill-counters.md 3.4 KB
- examples/telemetry-api/tool-custom-spans.md 2.1 KB
- examples/testing-observability/test-custom-spans.md 2.6 KB
- examples/testing-observability/test-log-correlation.md 3.1 KB
- examples/tracing-setup/basic-tracing.md 1.9 KB
- examples/tracing-setup/production-tracing.md 2.3 KB
- examples/vendor-integrations/coralogix-setup.md 2.3 KB
- references/metrics-endpoint.md 10 KB
- references/structured-logging.md 4.7 KB
- references/telemetry-api.md 11 KB
- references/testing-observability.md 5.7 KB
- references/tracing-setup.md 5.3 KB
- references/vendor-integrations.md 7.5 KB
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.
- 4d ago First seen · 217 lines · 177 tokens per session scan A 6fbaf4f7f315
frontmcp-observability is a skill published in the GitHub repository agentfront/frontmcp (146 stars, last pushed 2d ago), licensed Apache-2.0. It adds 177 tokens to every session and 3,110 once invoked, about $0.0009 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-30.
Other skills, from other repositories
Observability & Monitoring
Structured logging, metrics, distributed tracing, and alerting strategies.
golang-observability-opentelemetry
Instrumenting Go applications with OpenTelemetry for distributed tracing, Prometheus for metrics, and structured logging with slog.
Observability Checklist
Reviews a service or codebase against a full observability checklist — logs, metrics, traces, and alerting gaps.
opentelemetry-docs
OpenTelemetry — vendor-neutral observability: traces, metrics, logs, OTLP, Collector, SDKs, semantic conventions.
phoenix-observability
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.
phoenix-observability
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.