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/icesixgod/codex-trajectoryInstalling this writes the configuration, not the program: `./scripts/codex_trajectory_launcher` has to be on your PATH already, or the server will not start.
Wrote 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/icesixgod/codex-trajectory/codex-trajectory-codex-trajectory)<a href="https://agentmods.dev/mcp/icesixgod/codex-trajectory/codex-trajectory-codex-trajectory"><img src="https://agentmods.dev/badge/mcp/icesixgod/codex-trajectory/codex-trajectory-codex-trajectory/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/icesixgod/codex-trajectory/codex-trajectory-codex-trajectory"><img src="https://agentmods.dev/badge/mcp/icesixgod/codex-trajectory/codex-trajectory-codex-trajectory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
codex-trajectory 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
{
"codex-trajectory": {
"command": "./scripts/codex_trajectory_launcher",
"args": [
"run",
"--script",
"./scripts/codex_trajectory_mcp.py"
],
"cwd": ".",
"env_vars": [
"CODEX_HOME"
]
}
}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 · 14 lines scan A b97c7b3986e0
codex-trajectory is an MCP server published in the GitHub repository icesixgod/codex-trajectory (249 stars, last pushed 15d 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
codex-usage-tracker
MCP server "codex-usage-tracker" as configured in douglasmonsky/codex-usage-tracker. Launched with codex-usage-tracker _mcp.
robotmcp
Modular MCP server with Streamable HTTP, optional OAuth 2.1, Supabase auth, Cloudflare tunnel, and creator-only access control. Runs locally from the robotmcp.server Python package. Needs 4 environment variables to run.
multisim-mcp
Unofficial MCP server for NI Multisim Automation API. Runs locally from the multisim-mcp Python package. Needs 1 environment variable to run.
mcp-devils-advocate
MCP server "mcp-devils-advocate" as configured in AleBrito124356/mcp-devils-advocate. Runs locally from the mcp-devils-advocate Python package. Needs 1 environment variable to run.
woven
MCP server "woven" as configured in Ducksss/LifeHack-2026. Runs ./node_modules/tsx/dist/cli.mjs with node. Needs 2 environment variables to run.
mcp-solana-ico
MCP server "mcp-solana-ico" as configured in waifuai/mcp-solana-ico. Runs locally from the mcp-solana-ico Python package.