agentmods.dev

debugging-with-logsafe

debugging-with-logsafe is a skill for Claude Code, Codex from omarqx/logsafe. It costs 59 tokens per session (749 once invoked), scanned B, original, MIT.

A debugging workflow that sends structured application logs to a local server called logsafe and lets you inspect them by session, error level, and request trace.

In plain words
What is it for?
Use it to add logs to an application, reproduce a bug, inspect error and trace events, and follow one request across frontend and backend processes.
Why use it?
It makes reproducible bugs easier to follow by keeping related events together and narrowing investigation from errors to the surrounding request flow.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 0repo 3mo ago B scan 59 tokens original MIT

Good fit Use it to add logs to an application, reproduce a bug, inspect error and trace events, and follow one request across frontend and backend processes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/omarqx/logsafe/debugging-with-logsafe
View source ↗ omarqx/logsafe
Install

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.

Any agent
npx skills add omarqx/logsafe --skill debugging-with-logsafe
Clone the repo
git clone --depth 1 https://github.com/omarqx/logsafe

Made for: Claude Code, Codex.

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 debugging-with-logsafe

README.md
[![agentmods](https://agentmods.dev/badge/skills/omarqx/logsafe/debugging-with-logsafe/github.svg)](https://agentmods.dev/skills/omarqx/logsafe/debugging-with-logsafe)
Your own site
<a href="https://agentmods.dev/skills/omarqx/logsafe/debugging-with-logsafe"><img src="https://agentmods.dev/badge/skills/omarqx/logsafe/debugging-with-logsafe/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 debugging-with-logsafe

Your own site · 80×15
<a href="https://agentmods.dev/skills/omarqx/logsafe/debugging-with-logsafe"><img src="https://agentmods.dev/badge/skills/omarqx/logsafe/debugging-with-logsafe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 749 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. 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.00059 $0.00749
Opus 5.5 $0.00024 $0.00300
Sonnet 5.5 $0.00012 $0.00150
Haiku 4.5 $0.00006 $0.00075

Measured 1mo ago against content hash 4b54c5c79d1d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

debugging-with-logsafe scanned grade B with 2 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

`curl -s localhost:4600/v1/log -d '{"session_id":"bug-1234","source":"api","ns":"payment","level":"error","msg":"...","ctx":{...}}'`

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

description: Use when debugging a running application whose behavior you can reproduce — instrument the app with logsafe structured logging, reproduce the bug, and read the session narrow-first (errors → trace → widen).
packages/server/skills/debugging-with-logsafe/SKILL.md · 49 lines

How it starts

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

Debugging with logsafe

logsafe is a local log server (default http://127.0.0.1:4600). Apps POST structured events; you read them back as filterable sessions. Ordering is always server arrival order (seq) — never trust client ts for ordering.

Workflow

  1. Check the server. MCP: call list_sessions. HTTP: curl -s localhost:4600/api/health → {"ok":true}. If down, start it: npx @coglet/logsafe (background it; it binds 127.0.0.1 only). A running server also hosts MCP over HTTP at /mcp (claude mcp add --transport http logsafe http://127.0.0.1:4600/mcp) — no subprocess needed.
  2. Instrument the app under debug. Always set a fresh, descriptive session_label per attempt so the session is findable.
    • JS/TS: npm i @coglet/logsafe-client, then initLogsafe({ source: 'api', sessionLabel: 'bug-1234 attempt 1' }) and createLog('payment') → log.debug/info/warn/error(msg, ctx). Use createLog(ns).withTrace(id) to follow one request across processes — give the SAME trace id to frontend and backend.
    • Anything else: POST JSON to /v1/log — only msg is required: curl -s localhost:4600/v1/log -d '{"session_id":"bug-1234","source":"api","ns":"payment","level":"error","msg":"...","ctx":{...}}'
  3. Reproduce the bug with the instrumented app.
  4. Read narrow-first.
    • MCP: query_events(session_id, level: "error"), then query_events(session_id, trace: "<id>"), then widen (level: "warn,error", ns: "payment.*", q: "timeout").
    • HTTP: same params on GET /api/sessions/<id>/events.
    • Bulk analysis: GET /api/sessions/<id>/export.ndjson (one JSON per line).
  5. Live-tail while re-reproducing to watch cause → effect in order.
    • MCP: tail_session(session_id) right before triggering the bug — it waits (≤30s) and returns what arrived.
    • HTTP: curl -N localhost:4600/api/sessions/<id>/stream.
  6. Clean up instrumentation when fixed: grep the app for the ns values you added.

Read the full file on GitHub · 49 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. 1mo ago First seen · 49 lines · 59 tokens per session scan B 4b54c5c79d1d

Subscribe to this mod's changes

debugging-with-logsafe is a skill published in the GitHub repository omarqx/logsafe (0 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 749 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Debugging
Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens

ci-fixer

CI failures - read error, minimal fix, verify.

sipyourdrink-ltd/bernstein · 15 tokens