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 rajavijayach/electrobun-skills --skill electrobun-debugginggit clone --depth 1 https://github.com/rajavijayach/electrobun-skillsWrote 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/rajavijayach/electrobun-skills/electrobun-debugging)<a href="https://agentmods.dev/skills/rajavijayach/electrobun-skills/electrobun-debugging"><img src="https://agentmods.dev/badge/skills/rajavijayach/electrobun-skills/electrobun-debugging.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.00185 | $0.03343 |
| Opus 5 | $0.00093 | $0.01672 |
| Sonnet 5 | $0.00037 | $0.00669 |
| Haiku 4.5 | $0.00018 | $0.00334 |
Grade B, and why
electrobun-debugging scanned grade B 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 8d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt install build-essential How it starts
The opening of the file, as written. The whole thing — 591 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electrobun Debugging
Comprehensive debugging and troubleshooting guide for Electrobun applications.
Development Environment
Basic Development Setup
# Development mode with hot reload
bun run dev
# Development mode with verbose logging
DEBUG=* bun run dev
# Development mode with specific debug namespace
DEBUG=electrobun:* bun run dev
Environment Configuration
.env.development:
# Enable development features
NODE_ENV=development
DEBUG=electrobun:*
# DevTools always open
ELECTRON_ENABLE_DEVTOOLS=1
# Disable security warnings in dev
ELECTRON_DISABLE_SECURITY_WARNINGS=true
# Custom dev server port
DEV_SERVER_PORT=3000
Debugging Main Process
Console Logging
// Main process logs appear in terminal
console.log("Main process started");
console.error("Error in main process");
console.warn("Warning in main process");
// Structured logging
const logger = {
debug: (msg: string, data?: any) => {
if (process.env.DEBUG) {
console.log(`[DEBUG] ${msg}`, data || "");
}
},
info: (msg: string, data?: any) => {
console.log(`[INFO] ${msg}`, data || "");
},
error: (msg: string, error?: any) => {
console.error(`[ERROR] ${msg}`, error || "");
if (error?.stack) {
console.error(error.stack);
}
}
};
logger.info("Window created", { width: 1200, height: 800 });
logger.error("Failed to load file", error);
Bun Debugger
# Start with Bun debugger
bun --inspect run dev
# With breakpoint on first line
bun --inspect-brk run dev
# Connect with Chrome DevTools
# Open chrome://inspect in Chrome
# Click "inspect" on your process
Error Handling in Main
// Global error handlers
process.on("uncaughtException", (error) => {
logger.error("Uncaught exception", error);
// Show error dialog
dialog.showMessageBox({
type: "error",
title: "Application Error",
message: "An unexpected error occurred",
detail: error.message,
});
// Optional: restart or quit
// app.relaunch();
// app.quit();
});
process.on("unhandledRejection", (reason, promise) => {
logger.error("Unhandled rejection", { reason, promise });
});
// Window error handler
win.on("error", (error) => {
logger.error("Window error", error);
});
// RPC error handling
win.defineRpc({
handlers: {
async someHandler(args: any) {
try {
// Handler logic
return { success: true };
} catch (error) {
logger.error("RPC handler error", error);
throw error; // Re-throw to send to webview
}
}
}
});
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.
- 8d ago First seen · 591 lines · 185 tokens per session scan B b0dd46bc194e
electrobun-debugging is a skill published in the GitHub repository rajavijayach/electrobun-skills (11 stars, last pushed 6mo ago), licensed MIT. It adds 185 tokens to every session and 3,343 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.