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 ryan-haver/fusebase-mcp --skill dev-debug-logsgit clone --depth 1 https://github.com/ryan-haver/fusebase-mcpWrote 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/ryan-haver/fusebase-mcp/dev-debug-logs)<a href="https://agentmods.dev/skills/ryan-haver/fusebase-mcp/dev-debug-logs"><img src="https://agentmods.dev/badge/skills/ryan-haver/fusebase-mcp/dev-debug-logs/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/ryan-haver/fusebase-mcp/dev-debug-logs"><img src="https://agentmods.dev/badge/skills/ryan-haver/fusebase-mcp/dev-debug-logs.svg" alt="Reviewed on agentmods" width="80" 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.00080 | $0.01415 |
| Opus 5.5 | $0.00032 | $0.00566 |
| Sonnet 5.5 | $0.00016 | $0.00283 |
| Haiku 4.5 | $0.00008 | $0.00142 |
Grade A, and why
dev-debug-logs 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 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.
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.
This is a copy
100% identical to dev-debug-logs — 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Debug Logs
Important: This skill is for local development only. For logs from deployed app backends, use the remote-logs skill with
fusebase remote-logscommand.
When an app is run through:
fusebase dev start FEATURE_PATH
the CLI creates a per-session log directory inside the selected app directory:
<app-dir>/logs/dev-<timestamp>/
with these files:
browser-logs.jsonlaccess-logs.jsonlbackend-logs.jsonlfrontend-dev-server-logs.jsonl
Use this skill when debugging the local app runtime. These logs are local development artifacts only.
Which Log File To Read
browser-logs.jsonl
Use for:
console.log/console.erroroutput from the browser- uncaught browser errors
- unhandled promise rejections
- navigation/lifecycle events from the app page
Important:
- It only works when the app is opened through the CLI proxy started by
fusebase dev start - The CLI injects a browser debug script into proxied HTML pages automatically
- Records are JSON Lines; each line is one event
Typical fields:
timestamptypelevelmessageargserrorurlpathname
backend-logs.jsonl
Use for:
- backend stdout/stderr captured during
fusebase dev start - runtime errors printed by an app backend
- startup messages like port binding, env/config issues, and stack traces
Typical fields:
timestampappIdline
Important:
- If the app defines a dedicated backend dev command, the CLI captures that process directly
- If frontend and backend are started together from one
dev.commandusing tools likeconcurrently, the CLI attempts to capture the backend lane into this file as well - This file is line-based output, not structured request logs
access-logs.jsonl
Use for:
- requests made to
/apithrough the local proxy - request/response headers
- request/response bodies for small JSON/text payloads
- proxy failures between the CLI and the app/frontend dev server
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.
- 1mo ago First seen · 170 lines · 80 tokens per session scan A 9e5eb7ddb879
dev-debug-logs is a skill published in the GitHub repository ryan-haver/fusebase-mcp (8 stars, last pushed 3d ago), licensed MIT. It adds 80 tokens to every session and 1,415 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to dev-debug-logs, differing in 0 lines, and is treated as a copy.
dev-debug-logs compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| dev-debug-logsryan-haver/fusebase-mcp | Skill | 8 | 3d ago | MIT | A | 80 | Claude Code |
| systematic-debuggingopen-metadata/OpenMetadata | Skill | 16k | today | Apache-2.0 | A | 37 | Claude Code |
| log-error-digestzebbern/claude-code-guide | Skill | 4.7k | yesterday | MIT | A | 71 | Claude Code, Codex |
| cwv-optimizeradobe/skills | Skill | 320 | today | Apache-2.0 | A | 112 | Claude Code |
| ci-fixersipyourdrink-ltd/bernstein | Skill | 1.2k | today | Apache-2.0 | A | 15 | Claude Code, Codex |
| incident-response-incident-responsermyndharis/antigravity-skills | Skill | 2.0k | 24d ago | MIT | A | 36 | Claude Code |
| diagnosing-missing-recordingsPostHog/posthog | Skill | 41k | today | none | A | 76 | Claude Code, Codex |