If you're doing this to avoid entering passwords, then that implies that either you'll run an SSH agent on Production, or you'll keep an unencrypted private key there. If it's the latter, then the administrators of Production will have access to your development box.
But if I'm reading between the lines correctly, you're using this approach as a workaround because you can't add your dev key to authorized_keys on Production. In that case, there's a better way to get what you want.
If you're using OpenSSH, you can avoid entering the password multiple times even with password-based access, by using SSH connection sharing. Once you've configured this, you SSH into the server normally in one window, typing in your password as normal. In another window, you do your copying, and your SCP client finds and uses the existing connection with no password entry required.
To set this up:
$ mkdir ~/.ssh/cm_socket
And add the following to your
After this, SSH and SCP will look for a shared connection by default. If you want to make a second, non-shared connection for some reason, you can add
-S none to your command line.
For more info: