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/steph-dove/klaussy-agentsWrote 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/steph-dove/klaussy-agents/klaussy)<a href="https://agentmods.dev/mcp/steph-dove/klaussy-agents/klaussy"><img src="https://agentmods.dev/badge/mcp/steph-dove/klaussy-agents/klaussy/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/steph-dove/klaussy-agents/klaussy"><img src="https://agentmods.dev/badge/mcp/steph-dove/klaussy-agents/klaussy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
klaussy 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 12d 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
{
"klaussy": {
"command": "klaussy-mcp",
"args": [],
"env": {
"PYTHONUNBUFFERED": "1"
}
}
}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.
- 12d ago First seen · 9 lines scan A 4bd0a2f38f03
klaussy is an MCP server published in the GitHub repository steph-dove/klaussy-agents (16 stars, last pushed 15d 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-30.
Other mcp servers, from other repositories
create-packkit
Provider-neutral project generator for modern JS/TS — packages, CLIs, apps, services & full-stack repos — from a CLI or a web configurator, with an embedded API and safe upgrades. Runs locally from the create-packkit npm package.
backgen
MCP server "backgen" as configured in IbrahimKhaled19/BackGen. Runs D:/Projects/BackGen/dist/mcp/index.js with node.
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.
citeguard-cli
Check a bibliography for retracted papers -- retractions, corrections, and expressions of concern via Crossref (including Retraction Watch records). CLI, Python library, MCP server, GitHub Action. Runs locally from the citeguard-cli Python package.
tokens-studio-mcp
MCP server "tokens-studio-mcp" as configured in Blyawon/tokensStudioMCP. Runs locally from the tokens-studio-mcp npm package.
rewynd
MCP server "rewynd" as configured in SrinjoyDev/rewynd. Launched with rewynd mcp.