Borrowing it
Nothing to install: this file belongs to pareelamre/analyzing-llm-rationale. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pareelamre/analyzing-llm-rationale/main/.agents/skills/superlog-debug/SKILL.mdgit clone --depth 1 https://github.com/pareelamre/analyzing-llm-rationaleWrote 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/pareelamre/analyzing-llm-rationale/superlog-debug)<a href="https://agentmods.dev/skills/pareelamre/analyzing-llm-rationale/superlog-debug"><img src="https://agentmods.dev/badge/skills/pareelamre/analyzing-llm-rationale/superlog-debug.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.1 | $0.00075 | $0.03092 |
| Opus 5 | $0.00037 | $0.01546 |
| Sonnet 5 | $0.00015 | $0.00618 |
| Haiku 4.5 | $0.00007 | $0.00309 |
Grade A, and why
superlog-debug 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 7d 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 -i -X POST https://intake.superlog.sh/v1/traces \ This is a copy
100% identical to superlog-debug — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Superlog production debugging
When the user is investigating something happening in production, query their actual telemetry before reasoning about the code. Superlog ingests OpenTelemetry traces, logs, and metrics for the user's services — the answer to "why did this 500?" / "is the deploy healthy?" / "what changed?" is almost always in there.
When to activate
Activate as soon as the user signals they are looking into real production behavior. Examples:
- "users can't sign in" / "checkout is broken" / "this is 500ing in prod"
- "is the deploy healthy?" / "did my PR regress anything?"
- "what's our p95 on /api/foo right now?" / "how many errors in the last hour?"
- "what's been happening with the worker overnight?"
- An incident channel message, a Sentry/PagerDuty link, an on-call ping.
Skip when:
- The work is local only (worktree dev, tests, type errors, lint).
- The user already pasted the relevant logs / traces / span.
- The question is purely "how is this code structured?" with no prod angle.
Prerequisite: the Superlog MCP must be installed
The tools below are exposed by the Superlog MCP server. If they are not available in the current agent, install it first.
For Claude Code:
claude mcp add --transport http superlog https://api.superlog.sh/mcp
For Codex:
codex mcp add superlog --url https://api.superlog.sh/mcp
codex mcp login superlog
For Cursor and others: copy the mcpServers snippet from https://superlog.sh/ → Connect.
After install, restart the agent and authenticate via the OAuth flow the MCP triggers on first use.
First call every session
superlog.get_active_project
If it is not the project the user is debugging, switch:
superlog.list_projects
superlog.set_active_project { project_id: "<id>" }
You can also pass project_id on any individual call without changing session state. If the user has multiple environments wired as separate projects (e.g. prod vs staging), confirm which one before querying.
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.
- 7d ago First seen · 173 lines · 75 tokens per session scan A 416cc8deba5a
superlog-debug is a skill published in the GitHub repository pareelamre/analyzing-llm-rationale (0 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 3,092 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to superlog-debug, differing in 0 lines, and is treated as a copy.
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…
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.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.