Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/autogrammar/todo2codeWrote 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/autogrammar/todo2code/todo2code)<a href="https://agentmods.dev/mcp/autogrammar/todo2code/todo2code"><img src="https://agentmods.dev/badge/mcp/autogrammar/todo2code/todo2code/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/autogrammar/todo2code/todo2code"><img src="https://agentmods.dev/badge/mcp/autogrammar/todo2code/todo2code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
todo2code 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 1mo 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
{ "todo2code": { "command": "npx", "args": [ "-y", "todo2code" ] } }
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.
- 1mo ago First seen · 9 lines scan A 698c80fbc20a
todo2code is an MCP server published in the GitHub repository autogrammar/todo2code (0 stars, last pushed 28d ago), licensed Apache-2.0. 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
cozempic
The fast, Pythonic way to build MCP servers and clients. Runs locally from the fastmcp Python package.
mcp-audit
MCP Permission Auditor — scan, enumerate, and risk-score all locally configured MCP servers. Runs locally from the mcp-audits Python package.
regula
MCP server "regula" as configured in kuzivaai/getregula. Runs locally from the regula-ai Python package.
connhex-tools
MCP server "connhex-tools" as configured in compiuta-origin/connhex-tools. Runs locally from the connhex-tools Python package.
pagouse
MCP server "pagouse" as configured in gianlucamazza/pagouse. Runs locally from the pagouse Python package.
secret-scanner-cl
Local-first CLI, pre-commit hook and MCP server for detecting hardcoded secrets. Runs locally from the secret-scanner-cl Python package.