Improve or Develop a Drupal 7 User login/creation module

A Drupal 7 module that does the following: 1) Allows users with the right permission to create other users. E.g. users with role of 'parent' (referred to as user) can create user accounts for another user (referred to as subuser) with the role of 'kid'. a) This functionality is similar to the Subuser module ([login to view URL]), so a minimal adaptation of this module will be fine (i.e. producing a patch file is expected). b) To access the 'user/%user/subuser' path and to display 'Subuser' tab, the specific user ID indicated by '%user' should have permission to create subusers e.g. 'Create an kid' must be checked for the 'parent' role. c) On the 'user/%user/subuser' page, if 'Add subuser' link is clicked and the user has already exceeded the limit on number of subuser creation, then a message should appear that the 'Maximum number of allowed additions has been reached' and should be displayed on same page i.e. the 'user/%user/subuser' page. d) The page layouts for the User pages should be similar to that provided by the Better Login module ([login to view URL]) - this module can be installed. Template files similar to those used in Betterlogin module should be used for theming as necessary. e) The listing of subusers on the page should be done through a template file. It should show image/avatar of subuser, name, edit or remove. f) When subusers are being created by the user, the email field should be hidden but when submitted should be automatically set to the '[login to view URL]'. (Replace _at_ with @). There should be a module setting where the domain i.e. '[login to view URL]' can be specified. 2) Implement social login in addition to normal Drupal site registration. a) A user should be able to create account/login as a 'parent' role via the login form in (1) above b) It should be ensured that the 'parent' is above a certain specified age (via a setting). This check can be done against the age provided by the social authentication site or required to be entered at some point by a prompt. c) A robust social authentication library or module should be suggested and used upon approval. The implementation of the social login module must not disrupt page layout and arrangement of user pages or site redirect capability. Hybridauth module may be considered and may need to be adapted to function properly in the context of the above information. NB: *Meaningful error messages and guidance messages should be provided on all relevant pages. **Work prioritization is in order of listing. References: [login to view URL] [login to view URL] [login to view URL] [login to view URL]