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/AndrewAltimit/template-repoWrote 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/andrewaltimit/template-repo/reaction-search)<a href="https://agentmods.dev/mcp/andrewaltimit/template-repo/reaction-search"><img src="https://agentmods.dev/badge/mcp/andrewaltimit/template-repo/reaction-search/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/andrewaltimit/template-repo/reaction-search"><img src="https://agentmods.dev/badge/mcp/andrewaltimit/template-repo/reaction-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
reaction-search 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
{
"reaction-search": {
"httpUrl": "http://localhost:8024/messages",
"timeout": 5000
}
}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 Changed · -12 lines 705457fbaa3b
- 1mo ago First seen · 18 lines scan A a894d8086d85
reaction-search is an MCP server published in the GitHub repository AndrewAltimit/template-repo (134 stars, last pushed 1mo ago), licensed Unlicense. 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
runx
The governed runtime for agent skills. Search the catalog and inspect a skill before running it. Remote server at api.runx.ai.
aegis
Auto-instrument AI agent frameworks with runtime security. One line to govern LangChain, CrewAI, OpenAI, Anthropic — injection blocking, PII masking, action policy, audit trail. Zero code changes. Runs locally from the agent-aegis Python package. Needs 1 environment variable to run.
eu-ai-act-scanner
MCP server "eu-ai-act-scanner" as configured in Peaky8linders/eu-ai-act-scanner. Launched with eu-ai-act-scan-mcp.
whitepact
ResponsibleAI — Enterprise AI Governance Platform: trust scoring, bias detection, hallucination detection, guardrails, compliance (NIST AI RMF / EU AI Act / ISO 42001), cost intelligence, drift monitoring. Runs locally from the rai-governance-platform Python package. Needs 1 environment variable to run.
veriswarm-mcp
VeriSwarm MCP Server — Trust infrastructure for AI agents via Model Context Protocol. Runs locally from the veriswarm-mcp Python package.
kernel
Open proof-required execution kernel for consequential actions. Runs locally from the actenon-kernel Python package.