Borrowing it
Nothing to install: this file belongs to ruaan-deysel/unraid-management-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ruaan-deysel/unraid-management-agent/main/.github/prompts/Debug Collector Issue.prompt.mdgit clone --depth 1 https://github.com/ruaan-deysel/unraid-management-agentWrote 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/commands/ruaan-deysel/unraid-management-agent/debug-collector-issue)<a href="https://agentmods.dev/commands/ruaan-deysel/unraid-management-agent/debug-collector-issue"><img src="https://agentmods.dev/badge/commands/ruaan-deysel/unraid-management-agent/debug-collector-issue/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/commands/ruaan-deysel/unraid-management-agent/debug-collector-issue"><img src="https://agentmods.dev/badge/commands/ruaan-deysel/unraid-management-agent/debug-collector-issue.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.00010 | $0.00510 |
| Opus 5 | $0.00005 | $0.00255 |
| Sonnet 5 | $0.00002 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
Debug Collector Issue 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug a Collector Issue
Follow these steps to debug a hardware-specific collector failure.
Step 1: Identify the Failing Collector
Check the log file at /var/log/unraid-management-agent.log for errors. Look for:
PANICmessages (collector crashed)- Parse errors (unexpected output format)
- Command execution failures
Step 2: Reproduce the Issue
If possible, get the raw command output that the collector is trying to parse. Common commands:
| Collector | Command / Source |
|---|---|
| System | /proc/cpuinfo, /proc/meminfo, sensors |
| Disk | smartctl output |
| GPU | nvidia-smi, intel_gpu_top |
| UPS | apcaccess, upsc |
| Hardware | dmidecode |
| Network | ethtool, /sys/class/net/ |
| VM | virsh via go-libvirt |
| Docker | Docker Engine SDK |
Step 3: Compare Expected vs Actual Output
The collector's parsing logic expects a specific format. Compare:
- What format does the parsing code expect?
- What format does this hardware actually produce?
Check the relevant parsing code in:
daemon/lib/parser.go— INI file parsingdaemon/lib/dmidecode.go— DMI/SMBIOS parsingdaemon/lib/ethtool.go— Network interface parsingdaemon/services/collectors/*.go— Collector-specific parsing
Step 4: Add Fallback Logic
When different hardware produces different output:
- Don't remove support for the original format
- Add detection for the new format
- Use defensive parsing (check array bounds, handle nil)
- Log warnings for unexpected formats (not errors)
Step 5: Test
- Add test cases for both the original and new hardware formats
- Use actual output samples as test fixtures
- Run
make testto verify nothing broke
Step 6: Document
- Document the hardware details in the PR description
- Update
CHANGELOG.mdwith the fix - Consider updating
docs/guides/system-requirements.mdif relevant
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.
- 2d ago First seen · 67 lines · 10 tokens per session scan A 02923e98d27b
Debug Collector Issue is a command published in the GitHub repository ruaan-deysel/unraid-management-agent (53 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 510 once invoked, about $0.0001 per session on Opus 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-09-07.
Other commands, from other repositories
playground
Interactive WebSocket-based debugging environment for testing and developing agents.
gpu
Diagnose GPU health, discover bounded recipes, and collect typed numeric evidence without guessing from screenshots.
debug
A command-line debugging toolkit for embedded programs using J-Link or OpenOCD, tools that connect a computer to a microcontroller for inspection.
la
A command for capturing and decoding signals with a Saleae logic analyzer, a device that records electrical digital signals over time. It supports buses such as UART, SPI, and I2C, which are common ways chips communicate with peripherals.
map
A parser for Keil compiler map files, which are build reports describing where program code and data are placed in memory. It reports object sizes, memory regions, symbols, and stack or heap details.
verify
An embedded-device verification workflow that checks a development step through building, flashing firmware, debugging with J-Link, and reading serial logs. Firmware is software that runs directly on a microcontroller or other device.