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 orchidautomation/pluxx --skill pluxx-troubleshoot-installgit clone --depth 1 https://github.com/orchidautomation/pluxxWrote 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/orchidautomation/pluxx/pluxx-troubleshoot-install)<a href="https://agentmods.dev/skills/orchidautomation/pluxx/pluxx-troubleshoot-install"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/pluxx-troubleshoot-install/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/orchidautomation/pluxx/pluxx-troubleshoot-install"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/pluxx-troubleshoot-install.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.00029 | $0.00374 |
| Opus 5 | $0.00015 | $0.00187 |
| Sonnet 5 | $0.00006 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
pluxx-troubleshoot-install 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 9d 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
Pluxx Troubleshoot Install
Use this skill when the plugin already built or installed, but the host still does not look right.
Workflow
- Identify the host or hosts that still look broken.
- Start with install-state proof:
pluxx verify-install --target <platforms...>
- If the installed state still looks wrong or the user says the host UI is still stale, run deeper installed-bundle diagnosis:
pluxx doctor --consumer <installed-path>
- Use the verification and consumer-doctor output to classify the problem:
- bundle missing
- stale host cache
- stale marketplace/discovery state
- wrong runtime/auth materialization
- missing runtime payload
- reload/restart still required
- Return the smallest recovery action:
- reload or restart the host
- reinstall the plugin
- reinstall with
--trust - reinstall with the real env var exported
- rebuild before reinstall
Rules
- Findings come before reassurance.
- Do not say an install is healthy just because files exist on disk.
- Prefer
pluxx verify-installbefore guessing at host state. - Use
pluxx doctor --consumerwhen it materially improves diagnosis, not as ritual. - If you do not know the installed bundle path yet, derive it from the host target or from the verification output before guessing.
Output
- Say what failed and in which host.
- Say whether install-state proof passed or failed.
- If consumer diagnosis ran, summarize the key finding.
- End with the smallest next step that should actually unblock the user.
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.
- 9d ago First seen · 45 lines · 29 tokens per session scan A b0b907f32780
pluxx-troubleshoot-install is a skill published in the GitHub repository orchidautomation/pluxx (5 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 374 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-03.
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.