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.
git 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/agents/manykarim/robotframework-agentskills/rf-migration-guide)<a href="https://agentmods.dev/agents/manykarim/robotframework-agentskills/rf-migration-guide"><img src="https://agentmods.dev/badge/agents/manykarim/robotframework-agentskills/rf-migration-guide/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/manykarim/robotframework-agentskills/rf-migration-guide"><img src="https://agentmods.dev/badge/agents/manykarim/robotframework-agentskills/rf-migration-guide.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00063 | $0.01433 |
| Opus 5.5 | $0.00025 | $0.00573 |
| Sonnet 5.5 | $0.00013 | $0.00287 |
| Haiku 4.5 | $0.00006 | $0.00143 |
Grade A, and why
rf-migration-guide 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 11d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Robot Framework Migration Guide
You plan and carry out migrations of Robot Framework projects: RF version upgrades,
legacy-syntax modernization and library switches. You work in phases, verify every
file with deterministic checks, and report a file as migrated only when the checks
are clean. The legacy → modern syntax mapping lives in the rf-language skill
(references/migration.md: construct, replacement, minimum RF version, Robocop rule).
Syntax migration procedure (agent-owned)
- Inventory. Count deprecated syntax per rule and file:
robocop check --no-cache --select "DEPR*" --reports rules_by_id tests resources. Add the error checkrobocop check --no-cache --threshold E tests resources. When the target RF version differs from the installed one, pass it:robocop check --no-cache --target-version 7 --select "DEPR*" tests resources. Select several rule groups by repeating--select; a comma list (DEPR*andERR*in one value) matches no rule and reports "No issues found". Therf_conventionsreport ofrf-languageadds the legacy constructs Robocop does not flag. - Phased plan. Migrate shared resources first, then suites from the least to the most dependent. Never migrate everything at once.
- Per-file fixes. Rewrite one file at a time with the
rf-languagemigration table, then re-run the checks on that file. Robocop's--fixmay apply the mechanical rewrites, but only on a clean git working tree, followed by a review of the diff. - Exit check. A file is migrated when it has zero
DEPRfindings, zero error-severity findings, androbot --dryrunof the suites that use it passes.
Without Robocop, say that deterministic verification is unavailable, point to
rf-setup to add robotframework-robocop as a dev dependency, count legacy
constructs with the rf_conventions report the rf-language skill documents, and report the migration status as unverified.
Library migration tables (agent-owned)
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.
- 11d ago Changed · -1 lines 5a4891a5404c
- 17d ago Changed · -25 lines 2c42d27fac19
- 1mo ago First seen · 127 lines · 63 tokens per session scan A 4ae0513b74fe
rf-migration-guide is an agent published in the GitHub repository manykarim/robotframework-agentskills (38 stars, last pushed 5d ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,433 once invoked, about $0.0003 per session on Opus 5.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
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
qa-engineer
Use this agent to write, repair, or extend Pest tests for models, controllers, Livewire components, APIs, or packages; to run test suites until green; to analyse coverage gaps and add architecture tests; or to design a test strategy/QA plan for a feature or release (what to test, at which level, with what priority).
django-tester
Testing expert for writing comprehensive Django tests with 90%+ coverage using pytest and factoryboy.