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 skills add roedyrustam/vibes-plug --skill logging-error-tracking-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/logging-error-tracking-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/logging-error-tracking-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/logging-error-tracking-expert/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/skills/roedyrustam/vibes-plug/logging-error-tracking-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/logging-error-tracking-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 198 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00081 | $0.03390 |
| Opus 5.5 | $0.00032 | $0.01356 |
| Sonnet 5.5 | $0.00016 | $0.00678 |
| Haiku 4.5 | $0.00008 | $0.00339 |
Grade A, and why
logging-error-tracking-expert 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 3d 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 — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logging & Error Tracking Expert (2026 Edition)
English
Orchestration & Integration
- Upstream Orchestrators: Works under
brainstormingandzero-to-prod-orchestrator(Phase 7 - Monitoring & Production Telemetry) to provide unified logging and alert handling. - Downstream Cooperating Skills:
data-telemetry-expert— OpenTelemetry spans + log correlation.error-resilience-expert— Error tracking, circuit breakers, and monitoring setup.js-backend-expert— Server-side logging middleware (Fastify/Hono/Express).ci-cd-devops-architect— Source map upload in CI/CD pipelines.production-ready-hardener— Pre-launch logging and monitoring audit checklist.zero-trust-secret-vault— Secure redaction and logging of secret access patterns.session-memory-manager— Store error logs and operational telemetry states.
Description
Production-grade guide for implementing structured logging, error tracking, and application monitoring. Covers Pino (high-performance JSON logging), Sentry SDK integration (React, Node.js, Next.js), source map upload for production errors, request ID correlation across microservices, log aggregation (Axiom, Datadog, Logflare), alert rules, GDPR-compliant log redaction (PII masking), and OpenTelemetry integration.
Trigger Conditions
Activate this skill when:
- Setting up structured logging for Node.js/Bun backend services.
- Integrating Sentry for error tracking in React/Next.js apps.
- Implementing request ID correlation across microservices.
- Setting up log aggregation and search (Axiom, Datadog, Grafana Loki).
- Configuring alerting rules for production errors.
- Implementing GDPR-compliant log management (PII redaction).
- Setting up source map uploads for production debugging.
Logging Library Selection Guide
| Library | Best For | Performance | Output Format |
|---|---|---|---|
| Pino | High-throughput Node.js services | ⭐⭐⭐⭐⭐ (fastest) | JSON (structured) |
| Winston | Enterprise, multiple transports | ⭐⭐⭐ | Configurable |
| Bunyan | Legacy projects | ⭐⭐⭐⭐ | JSON |
| console.log | Never in production | ❌ | Unstructured |
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.
- 3d ago Changed aeba049b581b
- 4d ago Changed · +1 lines e2aa4865d794
- 7d ago Changed · +63 lines 59ac51ade24e
- 16d ago Changed 81d2a19d52f9
- 21d ago Changed 6fc98ec71658
- 22d ago Changed a5746d66257a
- 24d ago Changed · -6 lines · +67 tokens per session c42ad5d9843d
- 26d ago Changed · +6 lines · -67 tokens per session 1bf522370161
- 1mo ago Changed abd0d34072fb
- 1mo ago First seen · 345 lines · 81 tokens per session scan A 1b7350e3509b
logging-error-tracking-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (113 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 3,390 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
code-review
Reviews code for bugs, security issues, and best practices.
mantis-critic
Assesses the production viability of findings, filtering out debug-only features and assertion traps. Use when findings have been validated and you need to confirm they are triggerable in production release builds (with assertions disabled). Don't use for writing reproduction scripts or patches.
diagnosing-bugs
A structured process for diagnosing difficult software bugs and performance slowdowns. It starts by creating a repeatable pass-or-fail check, such as a failing test, HTTP request, command, or browser script.
mantis-patch
Generates minimal security fixes using transactional isolation (shadow directories or file backups), applies patches, and verifies them. Use when security findings are successfully reproduced and need patches applied and verified. Don't use for initial vulnerability research or reproduction payload generation.