Config Tools is a package of modules that help to manage your Drupal 8 configuration files. This includes two modules currently.
https://www.drupal.org/project/config_tools
This module allows to lock any configuration changes done via the Drupal admin UI. This can be useful in scenarios where for example configuration changes should not be done on the production environment, but only on staging or local environments.
https://www.drupal.org/project/config_readonly
Ever experienced that your site's configuration was overridden, by the configuration on the filesystem, when doing a drush cim?
This module is a tool to let you keep the configuration you want, in place.
Lets say that you do would like the system.site configuration (which contains that sites name, slogan, email, etc) to remain untouched, on your live site, no matter what the configuration, in the config folder, says.
Or maybe you are getting tired of having the devel.settings changed every time you import configuration?
https://www.drupal.org/project/config_ignore
The report module supplements the core Configuration Manager module, by providing a report that allows you to see the differences between the configuration items provided by the current versions of your installed modules, themes, and install profile, and the configuration on your site. The report is available from the administration UI, or via Drush commands.
https://www.drupal.org/project/config_update
Modules such as Config Split want to modify the configuration when it is synchronized between the database and the exported yaml files. This module provides the API to do so but does not influence a sites operation.
https://www.drupal.org/project/config_filter
The Drupal 8 configuration management works best when importing and exporting the whole set of the sites configuration. However, sometimes developers like to opt out of the robustness of CM and have a super-set of configuration active on their development machine and deploy only a subset. The canonical example for this is to have the devel module enabled or having a few block placements or views in the development environment and then not export them into the set of configuration to be deployed, yet still being able to share the development configuration with colleagues.
This module allows to define sets of configuration that will get exported to separate directories when exporting, and get merged together when importing. It is possible to define in settings.php which of these sets should be active and considered for the export and import.
https://www.drupal.org/project/config_split
Configuration inspector for Drupal 8 uses the core built-in configuration system as well as schema system to let you inspect configuration values and the use of schemas on top of them. This makes it possible to have a developer focused overview of all your configuration values and do various testing and verification tasks on your configuration schemas.
https://www.drupal.org/project/config_inspector
Config Suite is a set of improvements to the core config system that eases the experience of working with configuration.
https://www.drupal.org/project/config_suite
https://www.youtube.com/watch?time_continue=1&v=T0uNpkM1M9M
Demos config_suite
https://www.youtube.com/watch?&v=945cqoWem5I