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/UladzKha/samuraizer-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/uladzkha/samuraizer-cli/mcp-server-samuraizer)<a href="https://agentmods.dev/mcp/uladzkha/samuraizer-cli/mcp-server-samuraizer"><img src="https://agentmods.dev/badge/mcp/uladzkha/samuraizer-cli/mcp-server-samuraizer.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
samuraizer 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 6d 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
{
"samuraizer": {
"command": "npx",
"args": [
"-y",
"@samuraizer/mcp-server"
],
"env": {}
}
}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.
- 6d ago First seen · 10 lines scan A e42b6b270ba7
samuraizer is an MCP server published in the GitHub repository UladzKha/samuraizer-cli (0 stars, last pushed 9d 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
local-model-suitability-mcp
Check if a task runs locally vs cloud. Save money on calls that don't need cloud inference. Runs locally from the local-model-suitability-mcp npm package. Needs 1 environment variable to run.
svelte
MCP server "svelte", hosted remotely at mcp.svelte.dev, as configured in xinity-ai/xinity-ai.
greedy-token
MCP server "greedy-token" as configured in svasenkov/greedy-token. Launched with greedy-token-mcp. Needs 1 environment variable to run.
mcp-ollama
MCP server "mcp-ollama" as configured in true-alter/mcp-ollama. Runs locally from the @truealter/mcp-ollama npm package.
mailbridge
MCP server for IMAP/SMTP mailboxes: read, search, organize, draft and send mail from an AI assistant. Passwords stay in the macOS Keychain and mail is never deleted. Runs locally from the @marcocavanna/mailbridge npm package.
tokencompress
MCP server "tokencompress" as configured in jiawei686/tokencompress. Runs locally from the tokencompress Python package.