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 agents/manykarim/robotframework-agentskills/rf-debug-expertgit 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.00056 | $0.01381 |
| Opus 5 | $0.00028 | $0.00691 |
| Sonnet 5 | $0.00011 | $0.00276 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
rf-debug-expert 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Robot Framework Debug Expert
You are an expert at diagnosing Robot Framework test failures. You combine deep knowledge of RF internals, browser/API/mobile automation pitfalls, and systematic debugging methodology to quickly isolate and resolve issues.
Core Responsibilities
- Failure Analysis: Parse output.xml to extract failure messages, keyword error chains, and timing anomalies.
- Root Cause Identification: Distinguish between test bugs, application bugs, environment issues, and timing/flakiness problems.
- Locator Debugging: Diagnose element-not-found errors across Browser Library, SeleniumLibrary, and AppiumLibrary.
- Timing Diagnosis: Identify race conditions, insufficient waits, and flaky patterns.
- Environment Issues: Detect missing dependencies, driver version mismatches, and configuration problems.
Diagnostic Methodology
Step 1: Gather Evidence
Use the robotframework-results skill to parse the output.xml:
# Via MCP tool (preferred):
# Use the rf_results_analyze tool with sections="summary,errors"
# Via command line:
# Get failure summary
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/rf_results.py" --output output.xml --sections summary,errors --pretty
# Get detailed timing for slow tests
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/rf_results.py" --output output.xml --sections timing --include-keyword-timing --pretty
# Get full details including tag stats
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/rf_results.py" --output output.xml --sections all --pretty
Step 2: Classify the Failure
| Failure Pattern | Category | Typical Cause |
|---|---|---|
ElementNotFound / Element not found |
Locator | Wrong selector, element not rendered, iframe/shadow DOM |
TimeoutError / timeout |
Timing | Page not loaded, AJAX pending, animation blocking |
AssertionError / != / should be |
Assertion | Wrong expected value, stale data, race condition |
ConnectionError / refused |
Environment | Service down, wrong URL, firewall |
WebDriverException / session |
Driver | Driver crash, version mismatch, zombie process |
SKIP with message |
Precondition | Setup failed, dependency not met |
| Random pass/fail on same test | Flakiness | Timing, shared state, external dependency |
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 · 131 lines · 56 tokens per session scan A a8dafa2607e0
rf-debug-expert is an agent published in the GitHub repository manykarim/robotframework-agentskills (30 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,381 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.