|Think about Loose Coupling|
I think it's a question of format.
The first line you cant use :-), so write a comment into the second line of your code in the node. That means, when downloading code, your script has to parse the second line for the options "numbered=yes" or "no" and or any other things, so your little script will know if to strip line numbers or to mask them within comments. The authors information your script could include then anywhere within the file just using POD's author information and copyright notice, and if you want your script could even include the whole description from the original node within that POD.
Well, once more thinking about that, yes, I think perlmonks could generate such a file for you when you download the code. So you don't have to parse :-) but get a script with a nice "small(?)" POD, eh?
well perl can ..
Have a nice day
All decision is left to your taste
As perlmonks (or better to say Everything) uses XML why not to support tags when you post your script such as
just before or after the code or just somehow else