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-testcase-buildernpx skills add manykarim/robotframework-agentskills --skill robotframework-testcase-buildergit 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.00038 | $0.00611 |
| Opus 5 | $0.00019 | $0.00305 |
| Sonnet 5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
rf-testcase-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 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
98% identical to testcase-builder — 4 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Robot Framework Test Case Builder
Create test cases in Robot Framework syntax from structured input. Output JSON only.
Input (JSON)
Provide input via --input or stdin. Example:
{
"style": "keyword-driven",
"tests": [
{
"name": "User can create account",
"documentation": "Happy path account creation.",
"tags": ["smoke"],
"setup": {"keyword": "Open Browser", "args": ["${URL}", "chromium"]},
"teardown": {"keyword": "Close Browser"},
"steps": [
{"keyword": "Go To Sign Up"},
{"keyword": "Create User", "args": ["${username}", "${role}"]},
{"keyword": "User Should Be Logged In"}
]
}
]
}
Template-driven test:
{
"style": "template",
"tests": [
{
"name": "Login works",
"template": "Login Should Succeed",
"data_rows": [
["alice", "pass"],
["bob", "pass"]
]
}
]
}
Command
python scripts/testcase_builder.py --input tests.json
Flags
--allow-control-- Suppress warnings when control structures (FOR,IF,WHILE,TRY, etc.) appear in test steps. Without this flag the builder emits a warning for each control keyword found, encouraging you to move control logic into user keywords.--input FILE-- Path to the JSON input file (alternative to stdin).--full-suite-- Wrap the output in a*** Test Cases ***section so theartifactis a directly saveable, runnable.robotfile. Without it (the default) theartifactis a section fragment — the test case block(s) only, no header — meant to be embedded into an existing suite (e.g. one that already has*** Settings ***/*** Keywords ***).
Timeout support
Add "timeout" to a test object to render a [Timeout] setting:
{
"name": "Slow Operation",
"timeout": "30s",
"steps": [{"keyword": "Long Running Task"}]
}
Output (JSON)
artifact: test case block(s). A*** Test Cases ***section fragment by default; a full saveable suite when--full-suiteis passed.full_suite: whether the artifact includes the section header.warningsandsuggestions
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 · 88 lines · 38 tokens per session scan A 01fa75518afb
rf-testcase-builder is a skill published in the GitHub repository manykarim/robotframework-agentskills (30 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 611 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to testcase-builder, differing in 4 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.