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 MoonTzai/folderbridge-mcp --skill diagnosing-bugsgit clone --depth 1 https://github.com/MoonTzai/folderbridge-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/moontzai/folderbridge-mcp/diagnosing-bugs)<a href="https://agentmods.dev/skills/moontzai/folderbridge-mcp/diagnosing-bugs"><img src="https://agentmods.dev/badge/skills/moontzai/folderbridge-mcp/diagnosing-bugs/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/moontzai/folderbridge-mcp/diagnosing-bugs"><img src="https://agentmods.dev/badge/skills/moontzai/folderbridge-mcp/diagnosing-bugs.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.00025 | $0.00248 |
| Opus 5.5 | $0.00010 | $0.00099 |
| Sonnet 5.5 | $0.00005 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
diagnosing-bugs 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.
What it actually says
Diagnosing Bugs — FolderBridge Adaptation
For a hard bug, the first deliverable is a tight feedback loop that goes red on the user's actual symptom. Prefer a deterministic failing unit/integration/e2e test; otherwise use a minimal CLI harness, replay, differential check, or repeated stress loop. Do not build a theory from code reading before you can reproduce the failure.
Minimize the repro until unrelated variables are removed. Then generate several ranked, falsifiable hypotheses. Each hypothesis must predict what one targeted probe or controlled change would do. Instrument only at boundaries that distinguish those hypotheses; change one variable at a time.
Fix the smallest cause that explains the red signal, not nearby symptoms. Run the original repro first, then the relevant local tests, then the full regression suite. Keep a regression test that would have failed before the fix.
If the bug cannot be locked down because there is no stable test seam, treat that as an architecture finding and hand the seam problem to codebase-design / improve-codebase-architecture rather than hiding it with more logging or duplicated checks.
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 · 15 lines · 25 tokens per session scan A 851c215ef6ae
diagnosing-bugs is a skill published in the GitHub repository MoonTzai/folderbridge-mcp (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 25 tokens to every session and 248 once invoked, about $0.0001 per session on Opus 5.5. 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-31.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
mem0-status
Diagnoses mem0 connectivity, API key validity, and memory read/write functionality. Use when memory operations fail, searches return empty, addmemory errors occur, or to verify the plugin is working correctly.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
mem0-integrate
Integrate Mem0 into an existing repository using a goal-driven, TDD pipeline. Detects the repo's language automatically and asks the user to pick between Mem0 Platform (managed) and Mem0 Open Source (self-hosted). Writes failing tests before any implementation. Produces a local feature branch plus .mem0-integration/…
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
test-corpus
The testdocuments submodule is a bucket-fetched fixture corpus that is not committed. This skill covers readtestfixture, missing fixtures, valid A/B controls, and submodule push order. Load before running Rust tests on a fresh clone, setting up an A/B control, adding a fixture-backed test, or diagnosing…