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/vassiliylakhonin/agenda-intelligence-mdWrote 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/vassiliylakhonin/agenda-intelligence-md/agenda-intelligence)<a href="https://agentmods.dev/mcp/vassiliylakhonin/agenda-intelligence-md/agenda-intelligence"><img src="https://agentmods.dev/badge/mcp/vassiliylakhonin/agenda-intelligence-md/agenda-intelligence/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/vassiliylakhonin/agenda-intelligence-md/agenda-intelligence"><img src="https://agentmods.dev/badge/mcp/vassiliylakhonin/agenda-intelligence-md/agenda-intelligence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agenda-intelligence 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 2mo 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
{
"agenda-intelligence": {
"command": "uvx",
"args": [
"--from",
"agenda-intelligence-md",
"agenda-intelligence-mcp"
]
}
}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.
- 2mo ago First seen · 10 lines scan A e3c1fb097ac7
agenda-intelligence is an MCP server published in the GitHub repository vassiliylakhonin/agenda-intelligence-md (8 stars, last pushed yesterday), 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
pare-python
Pare Python ג€” Structured Python tool output (ruff, mypy, pip, uv, black, pytest) as typed JSON. Runs locally from the @paretools/python npm package.
validate
Deterministic validation for AI-generated artifacts: JSON Schema, OpenAPI response, SQL syntax. Runs locally from the @machinegrade/validate npm package. Needs 2 environment variables to run.
mcp-workspace
MCP server "mcp-workspace" as configured in MarcusJellinghaus/mcp-tools-py. Launched with ${MCP_CODER_VENV_PATH}\mcp-workspace.exe --project-dir ${MCP_CODER_PROJECT_DIR} . Needs 1 environment variable to run.
starlink-mcp-server
MCP server "starlink-mcp-server" as configured in ry-ops/starlink-enterprise-mcp-server. Runs locally from the starlink-mcp-server Python package.
waitbus
Workstation-local event bus and blocking wait/emit primitive: let any agent or script wait on or emit CI, pytest, Docker, and filesystem events without polling. GitHub Actions is source #1. Runs locally from the waitbus Python package.
pyeye
MCP server "pyeye" as configured in okeefeco/pyeye-mcp. Runs locally from the ${CLAUDE_PROJECT_DIR:-.} Python package.