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/keyword-buildernpx skills add manykarim/robotframework-agentskills --skill keyword-buildergit 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/keyword-builder)<a href="https://agentmods.dev/skills/manykarim/robotframework-agentskills/keyword-builder"><img src="https://agentmods.dev/badge/skills/manykarim/robotframework-agentskills/keyword-builder.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.00545 |
| Opus 5 | $0.00022 | $0.00272 |
| Sonnet 5 | $0.00009 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
keyword-builder 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- rf-keyword-builder — 91% identical, 6 lines differ
What it actually says
Robot Framework Keyword Builder
Create user keywords in Robot Framework syntax from structured input. Output JSON only.
Input (JSON)
Provide input via --input or stdin. Example:
{
"keyword_name": "Create User",
"description": "Creates a new user via the UI.",
"arguments": [
{"name": "username", "type": "str"},
{"name": "role", "default": "viewer"}
],
"tags": ["ui", "smoke"],
"setup": {"keyword": "Open Browser", "args": ["${URL}", "chromium"]},
"teardown": {"keyword": "Close Browser"},
"style": "simple",
"steps": [
{"keyword": "Click", "args": ["Add User"]},
{"keyword": "Input Text", "args": ["Username", "${username}"]},
{"keyword": "Click", "args": ["Save"]}
]
}
Command
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/keyword_builder.py" --input keyword.json
Detect embedded-argument style from an existing project:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/keyword_builder.py" --input keyword.json --project-root . --detect-embedded
Return values
Use "return_value" to add a RETURN statement at the end of the keyword:
{
"keyword_name": "Get Full Name",
"arguments": [{"name": "first"}, {"name": "last"}],
"steps": [{"assign": ["${result}"], "keyword": "Catenate", "args": ["${first}", "${last}"]}],
"return_value": "${result}"
}
Multiple return values:
"return_value": ["${var1}", "${var2}"]
Notes
- RF 7+ type annotations: Robot Framework 7 and later support type annotations
in
[Arguments]using${name}: typesyntax (e.g.${count}: int). This builder does not yet generate that syntax; type information is recorded in[Documentation]only.
Output (JSON)
artifact: keyword blockwarningsandsuggestionsmeta: any detected project conventions
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 · 76 lines · 44 tokens per session scan A 49f3e22b8e59
keyword-builder is a skill published in the GitHub repository manykarim/robotframework-agentskills (30 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 545 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-30.
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…