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/Avyayalaya/agent-councilWrote 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/avyayalaya/agent-council/agent-council)<a href="https://agentmods.dev/mcp/avyayalaya/agent-council/agent-council"><img src="https://agentmods.dev/badge/mcp/avyayalaya/agent-council/agent-council/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/avyayalaya/agent-council/agent-council"><img src="https://agentmods.dev/badge/mcp/avyayalaya/agent-council/agent-council.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-council 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
{
"agent-council": {
"command": "python",
"args": [
"${PLUGIN_ROOT}/mcp/agent_council_mcp_server.py"
],
"env": {
"COUNCIL_CONFIG": "${PLUGIN_ROOT}/council.yaml.example"
}
}
}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 · 11 lines scan A 45481473f429
agent-council is an MCP server published in the GitHub repository Avyayalaya/agent-council (10 stars, last pushed 1mo 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
shadcn
Add components to your apps. Runs locally from the shadcn npm package.
membridge
Cross-platform, cross-process shared memory with rwlock and SPSC ring buffer for Python, powered by Rust. Runs locally from the membridge Python package.
mcp-server
WasmAgent MCP server — WASM-sandboxed code execution with capability manifests and Tasks API. Runs locally from the @wasmagent/mcp-server npm package.
nexus-browser-mcp
A local browser-control MCP server built with Playwright and an accessibility tree. Playwright is software for controlling web browsers, while an accessibility tree describes page elements in a way automation tools can inspect.
mcp
Persistent memory for AI agents, governed by the human and stored on their own machine. Runs locally from the @mnemosyne_os/mcp npm package. Needs 2 environment variables to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.