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 pletor-ai/claude-code-pletor-plugin --skill troubleshootergit clone --depth 1 https://github.com/pletor-ai/claude-code-pletor-pluginWrote 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/pletor-ai/claude-code-pletor-plugin/troubleshooter)<a href="https://agentmods.dev/skills/pletor-ai/claude-code-pletor-plugin/troubleshooter"><img src="https://agentmods.dev/badge/skills/pletor-ai/claude-code-pletor-plugin/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/skills/pletor-ai/claude-code-pletor-plugin/troubleshooter"><img src="https://agentmods.dev/badge/skills/pletor-ai/claude-code-pletor-plugin/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.00040 | $0.00806 |
| Opus 5 | $0.00020 | $0.00403 |
| Sonnet 5 | $0.00008 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooter
You are diagnosing an error with a Pletor MCP operation. Follow the guidance below to resolve it quickly.
When to Use This Skill
Activate when:
- Any Pletor MCP operation returns an error
- You've retried an operation more than once without success
- You're unsure how to proceed after a failure
Upload Failures
| Symptom | Cause | Fix |
|---|---|---|
file_path not found / ENOENT |
Web MCP clients can't access local files | Use content_base64 instead. Read the file, base64-encode it, and pass with mime_type and filename. |
| "Could not determine MIME type" | No Content-Type header or unknown file extension | Pass mime_type explicitly (e.g., image/jpeg, video/mp4). |
| Upload succeeds but asset not usable | Forgot to provide filename | Always pass filename when using content_base64. |
Authentication and Connection Errors
| Symptom | Fix |
|---|---|
search_workflows or other Pletor tool not found |
Pletor MCP server isn't connected. Tell the user to run /mcp and enable Pletor. If not listed, they need to install the plugin first. |
| MCP call routed to wrong server (not Pletor) | Wrong MCP server is active. Tell the user to run /mcp, disable conflicting servers, and make sure Pletor is selected. |
| 401 from any operation | MCP token expired. Tell the user to run /mcp, select Pletor, and re-authenticate. |
| "fetch failed" or network error | Backend API not reachable. Ask the user to check if Pletor is running. |
Workflow Input Format Errors
This is the most common source of wasted retries. Never guess input formats.
The Golden Rule
Before passing inputs to run_workflow, always discover the schema:
- Call
get_workflowto read the DSL and identify input nodes (types ending with_input). - For well-known types, use these formats:
text_input→ plain stringimage_input/video_input/audio_input→{ "asset_ids": ["<asset_id>"] }
- For anything else → call
get_node_detailswith the node type to get the expected schema.
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 · 66 lines · 40 tokens per session scan A 432bed8f96db
troubleshooter is a skill published in the GitHub repository pletor-ai/claude-code-pletor-plugin (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 806 once invoked, about $0.0002 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-08-31.
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.