okay, so the account experience doesn't have a parameter for this. ultimately this is a multi-step process where first the login flow is initiated, and then you need a CSRF token to perform subsequent actions - that'll probably get in the way when hacking it.
if the scenario is that you always want to send the user directly to the Social Login provider, you might succeed by using json/API flows instead of browser/redirect flows, and build very minimal "UI" that does nothing but initializing and then passing on the user to the SSO provider