We should support updating an individual mod by slug.

Write up some documentation on the various commands.

Should probably add an open source license for this project.

Mod slugs to their IDs should be cached locally. A lite database or file could be used.

Should add a version flag or command that prints the current mmm version.
Currently the version flag is being used to specify a Minecraft version; this will likely need to be changed.

Add a list command to list the currently managed mods using the search table format.

It would probably be useful to provide the command run functions publicly.

The update command should support updating to a new Minecraft version for all mods.

An option could be added to allow update errors to occur without causing a revert of the config.
This could be useful in cases where a user wants to update all mods and does not care if some cannot be updated.

Mod slugs don't appear to always be found.

I think the downloaded mod files should probably use 755.

A configuration option should be added to support storing mods in a separate directory from the configuration file directory.

A new command should be added to download all mods listed in a configuration file.

Each command should better describe what it is doing.
Maybe some of this output should be hidden behind a verbose flag.
Will probably want some sort of logger with this functionality.

Allow specifying a mod loader for dependencies (i.e., Forge, Fabric).

It may be beneficial to allow individual mods to use a different version of Minecraft for cases where a mod supports a newer/older version of Minecraft even though it's not specified on CurseForge.

Would be a good idea to write some tests; already pretty behind 😞.

The add command's check for whether a mod should be skipped when downloading does not appear to be working.

Will want to switch to using something other than Viper to read and write mod dependency files.