Hi, Val... Like Andrew said, this is right up the alley of metascripts. While it sounds like you're adding the same text to every token's name, you will need differentiated results since starting with "Goblin" would be different than starting with "Wolf". That means in addition to TokenMod you'll want the Metascript Toolbox so you can use SelectManager's forselected handle to iterate over the tokens, and Fetch to pull the information at the correct time: !forselected(^) token-mod --set name|"@^(selected.token_name) NR" Removing the " NR" from the name would require another script from the Toolbox (don't worry, they all get installed if you install the Toolbox). Plugger lets you do a replace function, like this: !forselected(^) token-mod --set name|"{^&eval}replace(--source|"@^(selected.token_name)" --find|" NR"|""){^&/eval}" That would iterate over the tokens, looking for " NR" and replacing it with nothing. Note: I found a bug while verifying this syntax, and release a new version of Plugger. The update is in the pipeline for the 1-click, but I think I missed the deadline for this week's merge, so it won't happen until next week. If you install the Metascript Toolbox, you'll get the member scripts from the 1-click, and you'll get the fix automatically next week. BTW, if you want to quickly reference the tokens on the current page who have the " NR" text in their name, you can virtually select them without having to click on each one (or remember which ones are named that way). You would do that by adding this bit of syntax to your command line: {&select * NR} So, let's say you wanted to remove the " NR" from all tokens on the current page. You can use the previous example and add the {&select} syntax to arrive at: !forselected(^) token-mod --set name|"{^&eval}replace(--source|"@^(selected.token_name)" --find|" NR"|""){^&/eval}" {&select * NR}