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/manykarim/robotframework-agentskills/robotframework-libdoc-explainnpx skills add manykarim/robotframework-agentskills --skill robotframework-libdoc-explaingit clone --depth 1 https://github.com/manykarim/robotframework-agentskillsWhat 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.00050 | $0.00471 |
| Opus 5 | $0.00025 | $0.00235 |
| Sonnet 5 | $0.00010 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
rf-libdoc-explain 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.
This is a copy
95% identical to libdoc-explain — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Robot Framework Libdoc Explain
Use this skill to retrieve detailed keyword docs and argument usage from Robot Framework libraries/resources/suites. Output JSON only.
Command
Explain a keyword in standard libraries:
python scripts/rf_libdoc.py --library BuiltIn --keyword "Log" --pretty
Explain across multiple sources:
python scripts/rf_libdoc.py --library SeleniumLibrary --resource resources/common.resource --keyword "Open Browser" --pretty
Fallback to search if exact keyword not found:
python scripts/rf_libdoc.py --library SeleniumLibrary --keyword "Open Brows" --search "open browser" --pretty
Notes
- Use
--library,--resource,--suite, or--spec(repeatable). Inputs are aggregated. - Output contract (stable): every call returns
{schema_version, mode, libraries, results, ...}.modeis"explain"(exact keyword found),"fallback"(no exact match → search suggestions),"search", or"list".resultsis a single array; read it without branching on top-level keys. Each item is{library, keyword, usage, score, reasons}—usageis populated on explain/fallback,score/reasonson search; non-applicable fields arenull.usage.paramsis[{name, type, default, kind}]withkind ∈ required|optional|vararg|kwarg|named_only(nameis the bare param, no: type);usage.defaultsis keyed by bare name.
- Payload is bounded: library prose
docis not included by default. Pass--include-library-docto add each library's fulldoc/sourcetolibraries[]. - Use
--tag,--include-private,--exclude-deprecatedas filters.
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.
- 2d ago First seen · 38 lines · 50 tokens per session scan A 312315a6f51d
rf-libdoc-explain is a skill published in the GitHub repository manykarim/robotframework-agentskills (30 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 471 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to libdoc-explain, differing in 8 lines, and is treated as a copy.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.