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 agentmods add skills/pletor-ai/claude-code-pletor-plugin/startnpx skills add pletor-ai/claude-code-pletor-plugin --skill startgit clone --depth 1 https://github.com/pletor-ai/claude-code-pletor-pluginWhat 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 | $0.00024 | $0.00685 |
| Opus 5 | $0.00012 | $0.00342 |
| Sonnet 5 | $0.00005 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
start 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 3d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Welcome to Pletor
You are helping the user get started with Pletor, an AI workflow automation platform. Follow these steps:
Before You Begin
Tell the user:
Before connecting, make sure the Pletor MCP server is enabled. Run
/mcpin Claude Code, find Pletor in the list, and confirm it shows as connected. If you don't see it, install the Pletor plugin first.
Step 1: Verify Connection
Call the search_workflows MCP tool with an empty search and visibility: ["private"] to list only the user's private workflows. This verifies the connection and authentication.
If the call fails, identify which error occurred and respond with the matching guidance:
| Failure | How to detect | What to tell the user |
|---|---|---|
| Pletor MCP server not found | The search_workflows tool is not available or no matching MCP tool exists |
"The Pletor MCP server isn't connected. Run /mcp, look for Pletor, and enable it. If it's not listed, install the plugin first — see the README for instructions." |
| Wrong MCP server used | The call was routed to a server that is not Pletor | "It looks like the wrong MCP server was used. Run /mcp and make sure Pletor is the one enabled — disable any other servers that might conflict." |
| Expired or invalid token | Auth error such as 401 or "requires re-authorization" | "Your Pletor session has expired. Run /mcp, select Pletor, and re-authenticate. Your browser will open to sign in." |
Step 2: Show Summary
Once you have the private workflow list, present a friendly summary:
- How many private workflows the user has
- List the first 5 workflows by name with a brief description of each
- If the user has no private workflows, ask if they would like to see shared and public workflows instead. If they say yes, call
search_workflowswithvisibility: ["shared", "public"]and present those results.
Step 3: Show What's Possible
Tell the user they can interact with Pletor using natural language. Give these examples:
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.
- 3d ago First seen · 50 lines · 24 tokens per session scan A 85c999ac887c
start 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 24 tokens to every session and 685 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…