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/ShipToday/forge-plugin-codexWrote 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/shiptoday/forge-plugin-codex/forge-forge)<a href="https://agentmods.dev/mcp/shiptoday/forge-plugin-codex/forge-forge"><img src="https://agentmods.dev/badge/mcp/shiptoday/forge-plugin-codex/forge-forge/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/shiptoday/forge-plugin-codex/forge-forge"><img src="https://agentmods.dev/badge/mcp/shiptoday/forge-plugin-codex/forge-forge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
forge 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
{
"forge": {
"url": "https://teams.shiptoday.ai/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.
- 1mo ago First seen · 5 lines scan A f37e8478cbe5
forge is an MCP server published in the GitHub repository ShipToday/forge-plugin-codex (2 stars, last pushed 5d 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
mindtrain
MCP server "mindtrain" as configured in shigella520/MindTrain. Runs ./scripts/mindtrain_mcp_bridge.py with python3.
image_context_runtime
MCP server "imagecontextruntime" as configured in shixinnt/codex-image-context-runtime. Runs ./mcp/server.mjs with node.
registryBroker
MCP server "registryBroker" as configured in hashgraph-online/registry-broker-codex-plugin. Runs ./dist/cli.cjs with node.
xrocket
MCP server "xrocket" as configured in nakazanie-ton/myrocket. Runs ${PLUGIN_ROOT}/dist/cli.js with node. Needs 6 environment variables to run.
codex-win-to-wsl
MCP server "codex-win-to-wsl" as configured in Yuyu123fish/codex-win-to-wsl. Runs ./mcp/server.mjs with node.
proton-drive-cli
Manage Proton Drive from Claude, Codex, VS Code/Copilot, and other MCP clients through Proton's official CLI without exposing Proton credentials. Runs locally from the @borealstack/proton-drive-cli-mcp npm package.