Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/thijs-hakkenberg/mcp_todo/git-todo)<a href="https://agentmods.dev/mcp/thijs-hakkenberg/mcp_todo/git-todo"><img src="https://agentmods.dev/badge/mcp/thijs-hakkenberg/mcp_todo/git-todo/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/thijs-hakkenberg/mcp_todo/git-todo"><img src="https://agentmods.dev/badge/mcp/thijs-hakkenberg/mcp_todo/git-todo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
git-todo scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"git-todo": {
"command": "node",
"args": [
"/Users/thijshakkenberg/our_todo/dist/index.js"
],
"env": {
"TODO_REPO_PATH": "/Users/thijshakkenberg/my-todos",
"TODO_REPO_URL": "https://github.com/thijshakkenberg/my-todos.git",
"GIT_USER_NAME": "Thijs Hakkenberg",
"GIT_USER_EMAIL": "[email protected]",
"AUTO_SYNC": "true",
"SYNC_INTERVAL_SECONDS": "300",
"DEBUG": "true"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 17 lines scan A 5887e3aae1ad
git-todo is an MCP server published in the GitHub repository thijs-hakkenberg/mcp_todo (0 stars, last pushed 7mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
github-projects
GitHub's hosted MCP server: lets the agent search code, read and create issues and pull requests. Remote server at api.githubcopilot.com.
atlassian-mcp
MCP server for self-hosted Jira and Bitbucket (Go, distributed as a prebuilt binary). Runs locally from the @stubbedev/atlassian-mcp npm package.
keelen
Autonomous dev team steered from chat: plain-English requests in, tested merged PRs out. Remote server at keelen.ai.
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package.
atlassian-server-mcp
Unified stdio MCP server for Jira, Confluence, and Bitbucket Data Center. Runs locally from the @zaimokuza/atlassian-server-mcp npm package.
gitlab
GitLab MCP — wraps the GitLab REST API v4 (BYO API key). Remote server at gateway.pipeworx.io.