The libmongocrypt project lacks an Evergreen task to build and link one or more sample programs using the various available mechanisms (i.e., CMake, pkg-config, etc.). As a result, it is possible for the build to produce broken build helper scripts without the brokenness being detected until it is encountered by a user or downstream project. The C driver has a robust task which ensures that a sample program is built on each platform, using each available build mechanism, for both static and dynamic linking. It would be a good pattern to emulate in libmongocrypt to ensure that build helper scripts remain in a working state.