The following jstests all contain lists of commands to skip while they iterate through listCommands:

• jstests/core/views/views_all_commands.js
• jstests/sharding/database_versioning_all_commands.js
• jstests/sharding/safe_secondary_reads_drop_recreate.js
• jstests/sharding/safe_secondary_reads_single_migration_suspend_range_deletion.js
• jstests/sharding/safe_secondary_reads_single_migration_waitForDelete.js
• jstests/sharding/track_unsharded_collections_check_shard_version.js

If we make a map of commands in a file (ala jstests/lib/commands.js), then any author of a new command or a new listCommands using test can use that map and only touch one additional file instead of N tests x M commands.