Config Token

Allows the creation of custom tokens that are stored as config and exported via configuration manager.
It works in a similar way of Token Custom, the main difference is the storage.

The 'Custom Tokens' module, https://www.drupal.org/project/token_custom, works on a very similar way, the main difference is that it uses a custom entity to store the data whereas Config Token stores the data into configuration.

This allows users to export config to the config/sync folder and commit these changes.The custom tokens are managed by site builders and developers rather than normal users.
It is possible to import the config files to new/other sites instead of having to run queries to export/import the data from custom entities.

For more details, see the README.md on https://git.drupalcode.org/project/config_token

We had to implement it like this to be able to export config used by Domain Access module.

There is an alternative way of creating multiple tokens at once using CSV to Config