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/Johnny-xuan/TreeWorkInstalling this writes the configuration, not the program: `bash` has to be on your PATH already, or the server will not start.
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/johnny-xuan/treework/treework-treework)<a href="https://agentmods.dev/mcp/johnny-xuan/treework/treework-treework"><img src="https://agentmods.dev/badge/mcp/johnny-xuan/treework/treework-treework/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/johnny-xuan/treework/treework-treework"><img src="https://agentmods.dev/badge/mcp/johnny-xuan/treework/treework-treework.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
treework 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
{
"treework": {
"command": "bash",
"args": [
"./scripts/start-mcp.sh"
],
"cwd": "."
}
}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 04934de086dc
treework is an MCP server published in the GitHub repository Johnny-xuan/TreeWork (13 stars, last pushed 17d 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-30.
Other mcp servers, from other repositories
repogrammar
Local implementation-pattern context for coding agents. Runs locally from the @sioyooo/repogrammar npm package.
agentry-observability
Canonical Agentry discovery for coding agents: analytics, errors, deploys, and automation. Runs locally from the @agentrysh/mcp npm package.
vastlint
MCP server "vastlint" as configured in aleksUIX/vastlint. Launched with https://github.com/aleksUIX/vastlint/releases/download/v0.9.1/vastlint-mcp-linux.
doc-bridge
Resolve documentation ownership, edit roots, checks, and human handoffs before an agent edits code. Runs locally from the @agentskit/doc-bridge npm package.
gitpin
Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index. Runs locally from the gitpin npm package. Needs 1 environment variable to run.
micro
Official skill and local MCP tools for building and deploying Micro sites. Runs locally from the @microdotdo/micro-mcp npm package.