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 skills add mendixlabs/mxcli --skill migrate-oracle-formsgit clone --depth 1 https://github.com/mendixlabs/mxcliWrote 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/mendixlabs/mxcli/migrate-oracle-forms)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/migrate-oracle-forms"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/migrate-oracle-forms/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/skills/mendixlabs/mxcli/migrate-oracle-forms"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/migrate-oracle-forms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.03572 |
| Opus 5.5 | $0.00019 | $0.01429 |
| Sonnet 5.5 | $0.00009 | $0.00714 |
| Haiku 4.5 | $0.00005 | $0.00357 |
Grade A, and why
migrate-oracle-forms 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 5d 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 — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find it fast
sed -n '<from>,<to>p' SKILL.md one section rather than reading the file;
./mxcli syntax <topic> answers how do I write this for a fraction of either.
| lines | section |
|---|---|
| 31-38 | When to Use This Skill |
| 39-46 | Migration Overview |
| 47-79 | Reserved Word Conflicts |
| 80-159 | Script Organization |
| 160-220 | Validation Feedback |
| 221-300 | PL/SQL to Microflow Mapping |
| 301-360 | UI Component Mapping |
| 361-376 | Triggers to Microflows |
| 377-398 | Migration Checklist |
| 399-408 | Common Migration Errors |
| 409-418 | Tips for Success |
| 419-424 | Related Skills |
Oracle Forms to Mendix Migration Skill
This skill provides comprehensive guidance for migrating Oracle Forms applications to Mendix using MDL (Mendix Definition Language).
When to Use This Skill
Use this skill when:
- Converting Oracle Forms (.fmb) applications to Mendix
- Translating PL/SQL logic to Mendix microflows
- Mapping Oracle Forms UI elements to Mendix widgets
- Planning a migration strategy for legacy Oracle Forms systems
Migration Overview
Oracle Forms migration to Mendix involves:
- Data Model: Oracle tables → Mendix entities
- Business Logic: PL/SQL triggers/procedures → Mendix microflows
- User Interface: Forms blocks/items → Mendix pages/widgets
- Navigation: Form canvases → Mendix page navigation
Reserved Word Conflicts
Most common words (check, text, format, value, type, index, status, select, etc.) now work unquoted as attribute names in MDL. Only structural keywords (create, delete, begin, end, return, entity, module) need quoting.
Naming Best Practices
While most words are no longer reserved, using descriptive names is still recommended for clarity:
| Oracle Forms Field | Recommended Mendix Name | Notes |
|---|---|---|
check |
check or CheckStatus |
Works unquoted |
text |
text or TextContent |
Works unquoted |
format |
format or FormatType |
Works unquoted |
value |
value or FieldValue |
Works unquoted |
Name |
Name or ItemName |
Works unquoted (not a keyword) |
type |
type or ItemType |
Works unquoted |
create |
"create" or CreatedBy |
Requires quoting (structural keyword) |
delete |
"delete" or IsDeleted |
Requires quoting (structural keyword) |
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.
- 5d ago Changed · +21 lines 79ba4f6c4851
- 14d ago Changed 9ab9e9aaa4a0
- 15d ago Changed · -7 lines 7726524e4f02
- 16d ago Changed d8a16ab30f0c
- 1mo ago First seen · 411 lines · 47 tokens per session scan A e6c081e0b10b
migrate-oracle-forms is a skill published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 3,572 once invoked, about $0.0002 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 skills, from other repositories
hatch3r-api-spec
Generates and validates OpenAPI specifications from codebase. Covers endpoint design, schema validation, and documentation generation.
hatch3r-scalability-verify
Scalability verification gate before commit/release — stateless-handler ratio, back-pressure patterns, idempotency-key adoption, queue-based offloading, pool sizing, bulkheads, load-test pass at target scale.
golang-manual-di
Guides manual dependency injection wiring for Go services: three-tier naming taxonomy (Provide/MustProvide/Must), Must-pattern entrypoints, OS-signal-driven context lifecycle, common provider structs, infrastructure must-builders, interface-segregated bus registration, decorator/tracing wrappers, and…
terraform-infrastructure
Structures, writes, and reviews Terraform infrastructure code. Covers module layout, remote state, workspace strategy, variable and secrets handling, CI plan/apply pipeline, naming conventions, and multi-region deployment patterns (provider aliases, per-region state, failover strategies), while delegating shared risk…
microservices-architecture
Guides service boundary analysis, communication pattern selection, data consistency design, API contract strategy, and resilience checklist for microservices systems. Complements the microservices fragment. Invoked when the user asks to design a microservices system, split a monolith, or review service boundaries.
nosql-database-design
Designs a NoSQL data model by leading with access pattern analysis. Covers DynamoDB single-table design (PK/SK/GSI) and MongoDB embedding vs referencing, consistency models, and capacity planning. Invoked when the user asks to design a DynamoDB schema, MongoDB data model, or NoSQL data model.