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/DYZCODE/works-pluginsWrote 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/dyzcode/works-plugins/works-public)<a href="https://agentmods.dev/mcp/dyzcode/works-plugins/works-public"><img src="https://agentmods.dev/badge/mcp/dyzcode/works-plugins/works-public/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/dyzcode/works-plugins/works-public"><img src="https://agentmods.dev/badge/mcp/dyzcode/works-plugins/works-public.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
works-public 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
{
"works-public": {
"url": "https://works-runner.vercel.app/mcp-registry",
"type": "streamable-http"
}
}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 · 6 lines scan A db3c079a42d9
works-public is an MCP server published in the GitHub repository DYZCODE/works-plugins (0 stars, last pushed 2mo 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
foremerge
MCP server "foremerge" as configured in naw103/foremerge. Launched with foremerge mcp.
obsidian-github-mcp
MCP server "obsidian-github-mcp" as configured in SarutobiSasuke8/obsidian-github-mcp. Runs locally from the @sarutobi-sasuke/obsidian-github-mcp npm package.
commit-discipline-mcp
Plan and enforce small, test-gated Git commits through MCP or a CLI. Runs locally from the commit-discipline-mcp npm package.
okffs
MCP server connecting Claude Code to GitHub for an issue to branch to PR to close workflow. Runs locally from the @neturely/okffs npm package. Needs 3 environment variables to run.
branchlift
Stateful backend environments for parallel coding agents and git worktrees. Runs locally from the branchlift npm package.
github-mcp-sketch
MCP proxy in front of the GitHub MCP that returns inferred schemas instead of raw JSON, plus a queryresponse tool for drilling back into cached values. Built on json-schema-sketch. Runs locally from the github-mcp-sketch npm package.