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/HermeticOrmus/LibreUIUX-Claude-CodeWrote 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/plugins/hermeticormus/libreuiux-claude-code/distributed-debugging)<a href="https://agentmods.dev/plugins/hermeticormus/libreuiux-claude-code/distributed-debugging"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libreuiux-claude-code/distributed-debugging/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/plugins/hermeticormus/libreuiux-claude-code/distributed-debugging"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libreuiux-claude-code/distributed-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
distributed-debugging 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 15d 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
{
"name": "distributed-debugging",
"version": "1.2.0",
"description": "Distributed system tracing and debugging across microservices",
"author": {
"name": "Seth Hobson",
"url": "https://github.com/wshobson"
},
"homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code",
"repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code",
"license": "MIT",
"keywords": [
"distributed-tracing",
"microservices",
"debugging",
"observability"
]
}
What it installs
The manifest is a name and a version. 1 command, 1 agent travel with it, and installing the plugin installs all of them — 61 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 15d ago Changed · -9 lines 6bd3742cff52
- 1mo ago First seen · 28 lines scan A 119cd8c3a6d6
distributed-debugging is a plugin published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (115 stars, last pushed 11d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
distributed-debugging
Distributed system tracing and debugging across microservices.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
aio-golang-mastery
Write and lint idiomatic Go end-to-end — a 7-tool lint chain (build, vet, golangci-lint, govulncheck, nilaway, deadcode, race) plus reference-grade patterns for concurrency, errors, generics, gRPC, naming/style enforcement (revive 21-rule set, golangci-lint v2 production config), and production hardening.
aio-ios-device-debug
Debug iOS apps on physical devices. Build, install, launch, capture logs, pull crash reports, and analyze crashes from the terminal.
claude-adaptive-research
Autonomous, personalized research loops for Claude Code. Set a topic, walk away, come back to a quality-gated report adapted to your projects.
code-modernization
Guided modernization for any legacy codebase: start with /modernize, get an assessment, an interactive map, the business rules mined from the code, and a plan you approve, then an upgrade, a rewrite or a rebuild with independent proof that the new code behaves like the old. Includes security hardening, a one-page…