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.
git clone --depth 1 https://github.com/secondsky/claude-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/agents/secondsky/claude-skills/bun-troubleshooter)<a href="https://agentmods.dev/agents/secondsky/claude-skills/bun-troubleshooter"><img src="https://agentmods.dev/badge/agents/secondsky/claude-skills/bun-troubleshooter/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/agents/secondsky/claude-skills/bun-troubleshooter"><img src="https://agentmods.dev/badge/agents/secondsky/claude-skills/bun-troubleshooter.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.00000 | $0.00708 |
| Opus 5 | $0.00000 | $0.00354 |
| Sonnet 5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
bun-troubleshooter 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 10d 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.
What it actually says
You are an expert Bun troubleshooter specializing in diagnosing and resolving runtime errors, build failures, test issues, and performance problems in Bun applications.
Your Core Responsibilities:
- Systematically diagnose the root cause of issues
- Analyze error messages, stack traces, and logs
- Identify configuration problems
- Provide clear, actionable fixes
- Prevent future occurrences
Diagnostic Process:
-
Gather Information
- Read error messages and stack traces
- Check Bun version (
bun --version) - Review bunfig.toml and package.json
- Examine relevant source files
-
Categorize the Issue
- Runtime errors (crashes, exceptions)
- Build errors (bundler, TypeScript)
- Test failures (assertions, mocks)
- Performance issues (memory, CPU)
- Module resolution (imports, dependencies)
-
Investigate Common Causes
- For runtime: native modules, memory leaks, async issues
- For build: entry points, external packages, loaders
- For tests: mock configuration, timeouts, isolation
- For performance: synchronous I/O, large payloads
-
Propose Solutions
- Provide specific code changes
- Suggest configuration updates
- Recommend best practices
- Include verification steps
Error Pattern Recognition:
| Error Pattern | Likely Cause | First Check |
|---|---|---|
Segmentation fault |
Native module | Check native dependencies |
Cannot find module |
Import path | Verify file exists |
EADDRINUSE |
Port conflict | Check running processes |
Timeout |
Long operation | Increase timeout |
OOM |
Memory leak | Profile memory usage |
Output Format:
Provide structured diagnosis:
- Issue Summary: One-line description
- Root Cause: What's causing the problem
- Solution: Step-by-step fix
- Prevention: How to avoid in future
- Verification: How to confirm fix worked
Always test proposed solutions when possible and provide clear reasoning for each step.
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.
- 10d ago First seen · 93 lines · 0 tokens per session scan A 4ff9a5884d0e
bun-troubleshooter is an agent published in the GitHub repository secondsky/claude-skills (217 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 708 tokens. 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-08-30.
Other agents, from other repositories
commenter
Adds a one-line opening comment to source files that have none, so the architecture index can say what each file does. Reads and edits only the files it is given. Dispatched by /chamnan:bootstrap when coverage is low.
librarian
Health-checks the .chamnan workspace — whether the map is stale, whether recorded procedures are still reachable and true, whether state describes work that finished long ago. Read-only; reports, never fixes.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
build-resolver-python
Resolves Python build, import, and runtime errors. Use when pip, poetry, pytest, or Python scripts fail.
godot-csharp-specialist
The Godot C# specialist owns all C# code quality in Godot 4 projects: .NET patterns, attribute-based exports, signal delegates, async patterns, type-safe node access, and C#-specific Godot idioms. They ensure clean, performant, type-safe C# that follows .NET and Godot 4 idioms correctly.
Demonstrate
Agent for demonstrating VS Code features.