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.
npx agentmods add mcp/sethgammon/citadel/citadel-stategit clone --depth 1 https://github.com/SethGammon/CitadelWrote 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/sethgammon/citadel/citadel-state)<a href="https://agentmods.dev/mcp/sethgammon/citadel/citadel-state"><img src="https://agentmods.dev/badge/mcp/sethgammon/citadel/citadel-state.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
citadel-state 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 6d 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
{
"citadel-state": {
"command": "node",
"args": [
"mcp-servers/citadel-state/index.js"
],
"cwd": ".",
"env": {
"CITADEL_MCP_SERVER": "citadel-state"
},
"_codex": {
"startup_timeout_sec": 10,
"tool_timeout_sec": 30,
"required": false,
"instructions": "Use citadel_status to orient on campaign, fleet, telemetry, and artifact state before invoking Citadel workflows."
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 6d ago First seen · 18 lines scan A 50794743cd6f
citadel-state is an MCP server published in the GitHub repository SethGammon/Citadel (916 stars, last pushed 2d 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-30.
Other mcp servers, from other repositories
github
GitHub's hosted MCP server: lets the agent search code, read and create issues and pull requests. Remote server at api.githubcopilot.com.
wavedash
MCP server "wavedash", hosted remotely at mcp.wavedash.com, as configured in wvdsh/ai.
yonsei-bridge
MCP server "yonsei-bridge" as configured in mrcha033/yonsei-skills. Runs ./runtime/yonsei_bridge/mcp_server.py with python3.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.