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/Goldziher/polyWrote 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/plugins/goldziher/poly/plugin)<a href="https://agentmods.dev/plugins/goldziher/poly/plugin"><img src="https://agentmods.dev/badge/plugins/goldziher/poly/plugin/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/plugins/goldziher/poly/plugin"><img src="https://agentmods.dev/badge/plugins/goldziher/poly/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
poly 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 2d 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
{
"name": "poly",
"description": "Zero-dependency lint & format orchestrator over MCP — one pure-Rust binary wrapping ruff/oxc/taplo/rumdl and more as in-process backends, plus a tree-sitter generic tier for everything else. Exposes lint/format/cache tools with structured JSON output.",
"version": "0.29.0",
"author": {
"name": "Na'aman Hirschfeld",
"email": "[email protected]",
"url": "https://github.com/Goldziher"
},
"homepage": "https://github.com/Goldziher/poly",
"repository": "https://github.com/Goldziher/poly",
"license": "MIT",
"keywords": [
"linter",
"formatter",
"mcp",
"code-quality",
"rust"
],
"mcpServers": {
"poly": {
"command": "poly",
"args": [
"mcp"
]
}
}
}
What it installs
The manifest is a name and a version. 5 skills, 3 commands travel with it, and installing the plugin installs all of them — 253 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2d ago First seen · 29 lines scan A b078edfe536c
poly is a plugin published in the GitHub repository Goldziher/poly (20 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-15.
Other plugins, from other repositories
brand-identity-kit
Install this pack to generate a complete brand identity kit including logo, color palette, typography, and mockups.
code-security-review-pipeline
Audit code changes for bugs, security flaws, and quality issues before merging.
design-system-audit-and-remediation
Identify design debt, audit tokens, and enforce consistency across a product.
design-system-foundation
Create design tokens, principles, and naming conventions for a new design system.
agents-mcp
Build agents, MCP servers and tool-using workflows.
create-agent-skills
Scaffold, build, verify, and share a new agent skill with the team.