Sadly there is no real token replace in the default HTML module beyond a couple of simple [date]  and [portal.name] tags.
In the past it has been argued that the token replace system places too much of a performace load on the default tools - which is certainly the case
to a certain extent.

And there is no token replacement at all in the Header and Footer areas.

As a result - any more industrial strength token systems have been the realm of 3rd party module developers

We wound up building our own html module system to replace the default HTML module for just that sort of reason
 - that is to support full token based tagging at the module TEXT level - utilising the localization token.replace system as its basis.

We also handle Token replaces in Header and Footer in the same way - but again there is a performace hit for each token replace process.

Westa

It really is a pretty simple patch to add in to the HTML module - was about 3 lines of code - provided that you dont want token caching.

But the real catch comes with the INLINE HTML editing.

You need to set up the HTML to render with the [TAGS] as is when in EDIT mode - and only do the token replacement when in VIEW mode.

We also do the same thing for token replacement in the TITLE skin object

Westa