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 skills add agentprism/agentprism-workflows --skill run-codexgit clone --depth 1 https://github.com/agentprism/agentprism-workflowsWrote 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/skills/agentprism/agentprism-workflows/run-codex)<a href="https://agentmods.dev/skills/agentprism/agentprism-workflows/run-codex"><img src="https://agentmods.dev/badge/skills/agentprism/agentprism-workflows/run-codex/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/skills/agentprism/agentprism-workflows/run-codex"><img src="https://agentmods.dev/badge/skills/agentprism/agentprism-workflows/run-codex.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00039 | $0.00631 |
| Opus 5.5 | $0.00016 | $0.00252 |
| Sonnet 5.5 | $0.00008 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
run-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 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Real Codex Test
This skill runs real Codex with a prompt and captures all events for analysis during development.
When to Use
- Testing new event handlers
- Debugging event processing issues
- Understanding Codex response format and event order
- Validating implementation changes against real Codex behavior
- Seeing actual token usage, rate limits, and other metadata
How to Run
Execute the test script using npm:
npm run codex-test -- -p "Your prompt here"
Options
| Option | Short | Description | Default |
|---|---|---|---|
--prompt |
-p |
Prompt to send to Codex (required) | - |
--cwd |
-c |
Working directory for the session | Current dir |
--output |
-o |
Output format: all, codex, acp, summary |
all |
--json |
- | Output events as JSON | false |
--help |
-h |
Show help message | - |
Examples
# See all events for a simple prompt
npm run codex-test -- -p "What files are in this directory?"
# Test with specific working directory
npm run codex-test -- -p "Read the README" -c /path/to/project
# See only Codex events (raw server notifications)
npm run codex-test -- -p "Hello" -o codex
# See only summary (token usage, timing, event counts)
npm run codex-test -- -p "Hello" -o summary
# Get JSON output for analysis with jq
npm run codex-test -- -p "Hello" --json | jq '.method'
Output
The script outputs events in real-time as they arrive:
-
Codex Events (
[CODEX]): Raw events from Codex app serverthread/started,turn/started,turn/completeditem/started,item/completed,item/agentMessage/deltathread/tokenUsage/updated,account/rateLimits/updated
-
ACP Events (
[ACP]): Events sent to ACP connectionsessionUpdatewith various update types
-
Summary: Aggregated statistics
- Stop reason, duration, event counts
- Token usage breakdown (input, cached, output, reasoning, total)
- Event type frequency
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 75 lines · 39 tokens per session scan A 96a1215812d8
run-codex is a skill published in the GitHub repository agentprism/agentprism-workflows (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 631 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
rpa-init
Run when the user invokes /rpa-init or asks to onboard or warm up context on a repository. The agent studies code, reads documentation and test code, sets up the dev environment as the project expects, runs tests, and writes a short project report. No extra user brief is required.
rpa-gen-rules
Use when the user invokes /rpa-gen-rules or asks to create, refresh, audit, or synchronize project instructions such as root AGENTS.md, Cursor .cursor/rules, or Claude Code .claude/rules, especially when existing rule trees have drifted.
rpa-feat
Run when the user invokes /rpa-feat together with a clear feature description (for example issue text). BDD workflow: plan, failing tests, implementation, green tests, full suite, docs and examples, linter at the end. Will not work correctly without the user supplying what to build.
rpa-bugfix
Run when the user invokes /rpa-bugfix together with a clear bug description (expected vs actual, reproduction). Reproduction test first, then fix, full test suite, short report. Will not work correctly without the bug details.
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
ultra-adlc
End-to-end delivery orchestration for explicitly requested, very large software changes that must be completely implemented and independently proven. Use when the user invokes "ultra-adlc" or asks for an Ultra-ADLC-scale full delivery; do not use for ordinary features, small fixes, reviews, or ad hoc parallel work.