Git (MCP reference server) vs Superpowers

Git (MCP reference server)

Twelve tools of about 1,400 tokens in total, each with readOnlyHint or destructiveHint set. Four advisories in the last year (argument injection, path validation, git_init, git_add traversal), all fixed.

Superpowers

Fifteen MIT-licensed skills that make a coding agent design, plan, test first and review before it finishes, with five releases in 90 days and dated release notes. It has no CI workflow or security policy, its bootstrap insists a skill be invoked before any reply, and its optional visual companion loads a logo from Prime Radiant's site unless disabled.

Git (MCP reference server)

1. Pass repo_path on every call, even when the server was started with --repository
2. Use git_diff_staged before git_commit; commit takes whatever is staged and can't be undone through the server
3. Set max_count and a date range on git_log; diffs and git_show have no size cap
4. Send branch_type as one of local, remote or all; anything else returns an error string, not a schema error
5. Push with another tool; this server has no remote operations

Superpowers

1. Install it once per coding agent; each harness has its own install command, and the README says a second harness needs a second install.
2. Expect brainstorming to start before any code on a build request. Say so plainly if your human partner wants a quick change done without a design document.
3. Name a model on every subagent dispatch, as the skill asks; an unnamed subagent inherits the session's most expensive model.
4. Set SUPERPOWERS_DISABLE_TELEMETRY=1 before using the visual companion if no request may leave the machine.
5. Keep .superpowers/sdd/ out of git clean -fdx; it holds the progress ledger a resumed run reads.