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/URneiU1/codex-conversation-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/urneiu1/codex-conversation-council/conversation-council)<a href="https://agentmods.dev/mcp/urneiu1/codex-conversation-council/conversation-council"><img src="https://agentmods.dev/badge/mcp/urneiu1/codex-conversation-council/conversation-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/urneiu1/codex-conversation-council/conversation-council"><img src="https://agentmods.dev/badge/mcp/urneiu1/codex-conversation-council/conversation-council.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
conversation-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
{
"conversation-council": {
"command": "python3",
"args": [
"./scripts/council.py",
"serve-mcp"
],
"cwd": ".",
"env_vars": [
"CODEX_HOME",
"CODEX_THREAD_ID",
"COUNCIL_WORKSPACE",
"PLUGIN_DATA"
]
}
}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 · 16 lines scan A 455e0c6a8beb
conversation-council is an MCP server published in the GitHub repository URneiU1/codex-conversation-council (0 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
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.
veto
93 agentic MCP tools + 49 specialist agents for every major AI CLI. Self-learning, no API keys. Runs locally from the @jigyasudham/veto npm package.
draftrelay
MCP server "draftrelay" as configured in raashy/draftrelay. Runs locally from the draftrelay npm package.
repogrammar
Local implementation-pattern context for coding agents. Runs locally from the @sioyooo/repogrammar npm package.
droste-memory
MCP server "droste-memory" as configured in lorismascio17/droste-memory. Launched with powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\run_mcp.ps1. Needs 1 environment variable to run.
code-review-graph
Local-first knowledge graph for token-efficient code review through MCP and CLI. Runs locally from the code-review-graph Python package.