Tokens as a boilerplate?
There is a module that replace some tokens accepted from the Token module (or implemented using hook_token_info() and hook_tokens() in Drupal 7) in the body of a node, the Token Filter module.


  Token Filter is a very simple module to make token values available as an input filter.


There is then the Token Node Tokens (TNT) module that allows to define new tokens without implementing a module.


  TNT (Token Node Tokens) is a very simplistic module that allows you to create arbitrary tokens without having to create a custom module (i.e. /node/add/token). This was primarily created for use with the tokenize module so that through the UI a user could create tokens for use with CCK.


Unfortunately, this module has been declared unsupported, but looking at its code, you could create your custom module for doing the same thing.

An alternative is the Custom Tokens module.


  It gives the user the ability to create custom tokens for specific replacements that can improve other modules relying on the Drupal 7 token API or, for Drupal 6, the Token module.
  
  Versions 7.x-1.x and previours relied on PHP evaluation to build custom tokens.
  
  The new 7.x-2.x relies on input filters. While still allowing for PHP tokens through the D7 core PHP filter module, administrators can permit only HTML or plain text custom tokens.