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 commands/contoriumlabs/contorium/setup-mcp-codexgit clone --depth 1 https://github.com/ContoriumLabs/contoriumWrote 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/commands/contoriumlabs/contorium/setup-mcp-codex)<a href="https://agentmods.dev/commands/contoriumlabs/contorium/setup-mcp-codex"><img src="https://agentmods.dev/badge/commands/contoriumlabs/contorium/setup-mcp-codex.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00022 | $0.00323 |
| Opus 5 | $0.00011 | $0.00161 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade B, and why
setup-mcp-codex scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
This patches `~/.codex/config.toml` to use `node E:/sessionrecall/packages/mcp/bin/contorium-mcp.js` instead of `npx @contorium/mcp` (npx opens visible console windows). What it actually says
Setup Contorium for Codex
-
From the repository root:
npm run build:mcp(ornpm run compile). -
Plugin (recommended): install this repo as a Codex plugin (manifest at
.codex-plugin/plugin.json, MCP at.mcp.json). -
MCP only (local dev — recommended on Windows):
node scripts/setup-codex-mcp-local.mjsThis patches
~/.codex/config.tomlto usenode E:/sessionrecall/packages/mcp/bin/contorium-mcp.jsinstead ofnpx @contorium/mcp(npx opens visible console windows).Or manually:
codex mcp add contorium -- node E:/sessionrecall/packages/mcp/bin/contorium-mcp.js -
Do not use
npx @contorium/mcpon Windows — it spawnsnpm exec contorium bootstrapflash windows. -
Keep the Contorium VS Code/Cursor extension for sidebar UI and
.contora/state.json; Codex MCP tools complement the extension.
Tools: store_memory, search_memory, get_memory, get_workspace_context.
See docs/MCP.md and OpenAI Codex plugins.
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.
- 4d ago First seen · 23 lines · 22 tokens per session scan B a7891947fce4
setup-mcp-codex is a command published in the GitHub repository ContoriumLabs/contorium (6 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 323 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
om-vault-audit
Deep structural audit of the vault. Checks indexes, folder placement, frontmatter, links, Bases, and consistency. Fix what can be fixed, flag what needs user input.
om-incident-capture
Capture an incident from Slack channels, DMs, and threads into structured vault notes. Produces a complete incident work note with timeline, people, analysis, and brag doc entry.
om-intake
Process all unread meeting notes in work/meetings/ — reads each file, classifies content, routes to the right vault notes, then clears the inbox.
om-peer-scan
Deep scan a peer's GitHub PRs for performance review preparation. Produces a structured analysis saved to perf/evidence/.
om-dump
Freeform capture mode. Dump anything — conversations, decisions, incidents, wins, thoughts — and I'll route it all to the right notes with proper templates, frontmatter, and wikilinks.
session-stop
Stop recording and save this agent session to the project ledger.