keyword-builder

keyword-builder is a skill for Claude Code, Codex from manykarim/robotframework-agentskills. It costs 44 tokens per session (545 once invoked), scanned A, original, Apache-2.0.

A generator for Robot Framework user keywords. Robot Framework is a tool for writing readable automated tests, and user keywords are reusable groups of test steps.

In plain words
What is it for?
Creating browser or other automated test keywords from structured descriptions, including inputs, setup and cleanup steps, documentation, tags, and return values.
Why use it?
It reduces the manual work and formatting mistakes involved in writing these reusable test actions. It can also follow argument, tag, setup, teardown, and project-style settings.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the rf-agentskills plugin — 12 skills, 4 agents, 4 hooks shipped together

Install

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.

agentmods
npx agentmods add skills/manykarim/robotframework-agentskills/keyword-builder
Any agent
npx skills add manykarim/robotframework-agentskills --skill keyword-builder
Clone the repo
git clone --depth 1 https://github.com/manykarim/robotframework-agentskills

Made for: Claude Code, Codex.

Or install rf-agentskills, the plugin that ships this one along with the rest of its 12 skills, 4 agents, 4 hooks.

Wrote 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.

agentmods badge for keyword-builder

README.md
[![agentmods](https://agentmods.dev/badge/skills/manykarim/robotframework-agentskills/keyword-builder.svg)](https://agentmods.dev/skills/manykarim/robotframework-agentskills/keyword-builder)
Your own site
<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>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 545 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash 49f3e22b8e59, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/rf-agentskills/skills/keyword-builder/SKILL.md · 76 lines

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}: type syntax (e.g. ${count}: int). This builder does not yet generate that syntax; type information is recorded in [Documentation] only.

Output (JSON)

  • artifact: keyword block
  • warnings and suggestions
  • meta: any detected project conventions
Changes

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.

  1. 4d ago First seen · 76 lines · 44 tokens per session scan A 49f3e22b8e59

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens