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/varienos/agentic-workflow/codexgit clone --depth 1 https://github.com/varienos/agentic-workflowGrade A, and why
codex 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 yesterday.
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.
This is a copy
100% identical to codex — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"codex": {
"type": "stdio",
"command": "codex",
"args": [
"mcp-server"
],
"env": {}
}
}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.
- yesterday First seen · 10 lines scan A f69d3c30f283
codex is an MCP server published in the GitHub repository varienos/agentic-workflow (58 stars, last pushed 2mo 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. It is 100% identical to codex, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
redmine-mcp-server
MCP server that lets AI assistants manage Redmine issues, projects, wikis, and time tracking. Runs locally from the redmine-mcp-server Python package. Needs 12 environment variables to run.
workfile
MCP server "workfile" as configured in illodev/workfile. Runs node_modules/@illodev/workfile/dist/bin/workfile.js with node.
sprint-mcp-local
MCP server "sprint-mcp-local" as configured in cnavta/sprint-mcp. Runs /Users/christophernavta/IdeaProjects/sprint-mcp/dist/index.js with node. Needs 3 environment variables to run.
vibeops-tracker
VibeOps Tracker: a local-first issue tracker. Capture, triage, and ship work across all your side projects with an embeddable widget, a Kanban board, markdown storage, and an MCP server that lets AI coding agents work your backlog. Runs locally from the vibeops-tracker npm package.
backloggd-mcp
MCP server "backloggd-mcp" as configured in DenisionSoft/backloggd-mcp. Runs locally from the backloggd-mcp npm package.
board
MCP server "board" as configured in kyzodb/plan. Runs locally from the ${CLAUDE_PLUGIN_ROOT} Python package. Needs 5 environment variables to run.