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-works-public)<a href="https://agentmods.dev/mcp/dyzcode/works-plugins/works-public-works-public"><img src="https://agentmods.dev/badge/mcp/dyzcode/works-plugins/works-public-works-public.svg" alt="Measured on agentmods" 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 7d 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": {
"type": "http",
"url": "https://works-runner.vercel.app/mcp"
}
}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.
- 7d ago First seen · 6 lines scan A 0d379a883aa4
works-public is an MCP server published in the GitHub repository DYZCODE/works-plugins (0 stars, last pushed 1mo 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
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.
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.
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.
branchlift
Stateful backend environments for parallel coding agents and git worktrees. Runs locally from the branchlift npm package.
taskgrade
Local task classification for coding-agent model selection. Runs locally from the taskgrade npm package.
agentry-observability
Canonical Agentry discovery for coding agents: analytics, errors, deploys, and automation. Runs locally from the @agentrysh/mcp npm package.