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/tool-guidenpx skills add pletor-ai/claude-code-pletor-plugin --skill tool-guidegit 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/tool-guide)<a href="https://agentmods.dev/skills/pletor-ai/claude-code-pletor-plugin/tool-guide"><img src="https://agentmods.dev/badge/skills/pletor-ai/claude-code-pletor-plugin/tool-guide.svg" alt="Measured on agentmods" 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 | $0.00044 | $0.00613 |
| Opus 5 | $0.00022 | $0.00307 |
| Sonnet 5 | $0.00009 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
tool-guide 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 4d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tool Guide
You are helping the user explore and learn about the Pletor platform.
When to Use This Skill
Activate when the user:
- Wants to find workflow templates for a specific use case
- Asks how a node type works or what it can do
- Needs help from Pletor documentation
- Wants to browse tutorials or guides
- Asks "what can Pletor do?" or similar exploratory questions
Documentation Search
-
Search docs — Call
search_documentationwith the user's question to find relevant documentation about Pletor features, nodes, models, or workflows. -
Search resources — Call
search_resourcewith keywords to find tutorials, guides, and reference agents. -
Fetch content — If a search result looks relevant, call
get_resource_contentwith the result'sidto fetch the full markdown content. Present it clearly to the user.
Tips for good searches
- Use specific terms: "image generation node" rather than "how to make images"
- If the first search returns no results, try rephrasing with different keywords
- Combine doc search with resource search for broader coverage
Template Discovery
-
Browse tags — Call
list_template_tagsto see available use-case and industry tags. This helps narrow the search. -
Search templates — Call
search_templateswith:searchfor text-based matching on template namesuse_case_tagsand/orindustry_tagsfor tag-based filtering- Both can be combined
-
Present results — Show templates with their names, descriptions, and what they do. If the user likes a template, suggest they run it using natural language (the workflow-runner skill handles execution).
Node Details
Call get_node_details with the node type to explain:
- What the node does
- What inputs it accepts (its schema)
- Which AI models are compatible with it
- Optionally filter by a specific
modelto see model-specific configuration
Common node types
image_generation— Generate images from text promptsvideo_generation— Generate videos from text or imagesllm— Large language model text generationimage_editing— Edit or transform existing imagesaudio_generation— Generate audio or musicspeech_to_text— Transcribe audio to text
What ships with it
1 file beside SKILL.md 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.
- 4d ago First seen · 68 lines · 44 tokens per session scan A e4a99e78a1aa
tool-guide 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 44 tokens to every session and 613 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
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
ljg-learn
Deep concept anatomist that deconstructs any concept through 8 exploration dimensions (history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philosophy) and compresses insights into an epiphany. Use when user asks to explain, dissect, or deeply understand a concept, term, or…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
grid-ctf-ops
Operational knowledge for the gridctf scenario including strategy playbook, lessons learned, and resource references. Use when generating, evaluating, coaching, or debugging gridctf strategies.