There's the "/terminal inkey" command, which asks the user for a single key, and returns the key code of the pressed key, which you can then decode into an ASCII character or a keyboard key.
It's as cumbersome to work with as it sounds... You need to invoke it as many times as the number of characters you need, or more precisely, keep invoking it until a new line is entered (character code 13). Oh, and you better support backspace (character code 8 ) too. If you manage to elegantly abstract away such stuff, you may as well create a function for that... One which wouldn't need prompts upon
its install
. But at that point, I think we can agree that's overkill.