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/ssdeanx/ssd-aiWrote 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/ssdeanx/ssd-ai/hi-ai)<a href="https://agentmods.dev/mcp/ssdeanx/ssd-ai/hi-ai"><img src="https://agentmods.dev/badge/mcp/ssdeanx/ssd-ai/hi-ai/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/ssdeanx/ssd-ai/hi-ai"><img src="https://agentmods.dev/badge/mcp/ssdeanx/ssd-ai/hi-ai.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hi-ai 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 9d 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
{ "hi-ai": { "command": "npx", "args": [ "-y", "@ssdeanx/hi-ai" ] } }
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.
- 9d ago First seen · 9 lines scan A b1034e83d1ac
hi-ai is an MCP server published in the GitHub repository ssdeanx/ssd-ai (3 stars, last pushed 8mo 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
cas-genesis-world-mcp
MCP server for the CAS genesisWorld REST Webservice v7.0 — tools, flows, and resources with an optional read-only mode. Runs locally from the cas-genesis-world-mcp npm package.
atelier-quality-gate
Two-agent post-generation quality gate (UI/UX Critic & Backend Architecture Guard) for vibe-coded apps. Runs locally from the atelier-quality-gate npm package.
github
MCP server "github" as configured in dj-pearson/MCPFold. Launched with mcpfold run github.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
mcp-server-zotero-dev
MCP server enabling AI assistants to build, test, and debug Zotero plugins. Runs locally from the @introfini/mcp-server-zotero-dev npm package. Needs 2 environment variables to run.
saidsef-mcp-github-pr-issue-analyser
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.… Remote server at server.smithery.ai.