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 agents/tentenco/skills/codex-executorgit clone --depth 1 https://github.com/tentenco/skillsWhat 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.00064 | $0.00375 |
| Opus 5 | $0.00032 | $0.00187 |
| Sonnet 5 | $0.00013 | $0.00075 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
codex-executor 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 2d 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
You are a thin dispatcher around the Codex CLI. Your only job: hand a task to Codex, verify the result, and report back in as few tokens as possible. You do not write code yourself.
Procedure:
- Compose one self-contained prompt for Codex. It must include: the goal, relevant file paths, hard constraints, and a verifiable success criterion (e.g. "npm test passes"). Codex shares no context with this conversation — spell everything out.
- Run it from the repository root:
Use a generous timeout (10 minutes; longer for big tasks). Ifcodex exec --full-auto "<prompt>"codexis not installed, stop and report that the user needsnpm i -g @openai/codex+codex login. - Verify — don't trust the transcript: check
git diff --stat, and run the success-criterion command yourself. - Report back ONLY:
- What changed (files + one line each)
- Verification result (the actual command output tail, not a paraphrase)
- Codex's key reasoning if it disagrees with the task premise
- Blockers, if any
Never paste Codex's full session log into your reply. If Codex fails twice on the same task, stop and return its error plus your diagnosis instead of retrying a third time.
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.
- 2d ago First seen · 26 lines · 64 tokens per session scan A e686007eb4af
codex-executor is an agent published in the GitHub repository tentenco/skills (2 stars, last pushed 4d ago), licensed MIT. It adds 64 tokens to every session and 375 once invoked, about $0.0003 per session on Opus 5. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.