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/cooldk/clize-cliWrote 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/cooldk/clize-cli/clize)<a href="https://agentmods.dev/mcp/cooldk/clize-cli/clize"><img src="https://agentmods.dev/badge/mcp/cooldk/clize-cli/clize/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/cooldk/clize-cli/clize"><img src="https://agentmods.dev/badge/mcp/cooldk/clize-cli/clize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
clize 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
{ "clize": { "command": "npx", "args": [ "-y", "@clize/clize", "@clize/clize", "clize-mcp" ], "env": {} } }
What else
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 12 lines scan A c848a7541ad7
clize is an MCP server published in the GitHub repository cooldk/clize-cli (0 stars, last pushed 16d 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
azure-resource-manager-mcp
MCP server "azure-resource-manager-mcp", hosted remotely at mcp.management.azure.com, as configured in microsoft/skills.
AWSPrice
MCP server "AWSPrice" as configured in spacehendrix/clauder. Runs locally from the awslabs.aws-pricing-mcp-server@latest Python package. Needs 3 environment variables to run.
cloud-finops
MCP server exposing the OptimNow Cloud FinOps skill (reference library + named-pattern playbooks) as queryable tools. Runs locally from the cloud-finops-mcp Python package.
infracost
MCP server "infracost" as configured in DownAtTheBottomOfTheMoleHole/infracost-mcp. Runs ./dist/index.js with node.
cloudscope
Azure + GCP cost management: spending, forecasts, anomalies, budgets, idle resources, and tags. Runs locally from the cloudscope-mcp npm package. Needs 9 environment variables to run.
domain-intelligence
WHOIS, DNS records, SSL certificate data for any domain in one call. x402. Remote server at domain-intelligence.api.klymax402.com.