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-searchnpx skills add manykarim/robotframework-agentskills --skill robotframework-libdoc-searchgit clone --depth 1 https://github.com/manykarim/robotframework-agentskillsWrote 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/manykarim/robotframework-agentskills/robotframework-libdoc-search)<a href="https://agentmods.dev/skills/manykarim/robotframework-agentskills/robotframework-libdoc-search"><img src="https://agentmods.dev/badge/skills/manykarim/robotframework-agentskills/robotframework-libdoc-search.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.00049 | $0.00397 |
| Opus 5 | $0.00024 | $0.00198 |
| Sonnet 5 | $0.00010 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
rf-libdoc-search 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.
This is a copy
97% identical to libdoc-search — 6 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 Search
Use this skill to search Robot Framework libraries/resources/suites for keywords that match a use case. Output JSON only.
Command
Search in standard libraries:
python scripts/rf_libdoc.py --library BuiltIn --library OperatingSystem --search "create temp file" --pretty
Search multiple sources with custom weights:
python scripts/rf_libdoc.py --library SeleniumLibrary --resource resources/common.resource --search "upload file" --weights name=0.5,short_doc=0.3,doc=0.2 --limit 10 --pretty
Notes
- Use
--library,--resource,--suite, or--spec(repeatable). Inputs are aggregated. - Search considers keyword name,
short_doc, and fulldoc. - Output contract (stable): returns
{schema_version, mode, libraries, results, query, ...}withmode="search".resultsis a single array of{library, keyword, usage, score, reasons}(search items carryscore/reasons;usageisnull). Readresultswithout branching on top-level keys. - Payload is bounded: library prose
docis not included by default — only{name, type, version, scope, doc_format, short_doc}per library. Pass--include-library-docto add the fulldoc. - Use
--tagto filter keywords by tag. - Use
--include-privateto include private keywords. - Use
--exclude-deprecatedto drop deprecated keywords.
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.
- 3d ago First seen · 32 lines · 49 tokens per session scan A e78c6d85a897
rf-libdoc-search is a skill published in the GitHub repository manykarim/robotframework-agentskills (30 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 397 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to libdoc-search, differing in 6 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.
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…