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 skills/rebornix/agmente/codex-local-cli-e2enpx skills add rebornix/Agmente --skill codex-local-cli-e2egit clone --depth 1 https://github.com/rebornix/AgmenteWhat 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.00063 | $0.00656 |
| Opus 5 | $0.00032 | $0.00328 |
| Sonnet 5 | $0.00013 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
codex-local-cli-e2e 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 3d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Local CLI E2E
Overview
Run Agmente's Codex UI E2E test against a real local codex app-server, using the repo-owned scenario spec as the source of truth, collect actionable failure details, and always clean up simulator/app-server state.
Workflow
- Resolve run inputs.
- Require
endpoint(for examplews://127.0.0.1:8788) and simulatorUDID. - Decide run mode:
existing server: server already running.managed server: start server with a provided command and stop it during cleanup.
- Read
e2e/scenarios/codex/local-cli-smoke.md. - Use
references/agmente-codex-e2e-contract.mdonly for the UI-test environment-variable harness contract.
- Start or verify server.
- If
managed server, start the command and wait until the endpoint port is reachable. - If
existing server, verify reachability before running tests.
- Run only the Codex UI E2E test.
- Export:
AGMENTE_E2E_CODEX_ENABLED=1AGMENTE_E2E_CODEX_ENDPOINT=<endpoint>
- Execute targeted test only:
AgmenteUITests/AgmenteUITests/testCodexDirectWebSocketConnectInitializeAndSessionFlow
- On failure, extract root cause.
- Parse
xcodebuildoutput for the failing test and assertion. - Read
.xcresultdetails whenxcodebuildis not explicit. - Include failing file/line and endpoint/simulator context in the report.
- Always clean up.
- Stop app-server if this run started it.
- Uninstall app from simulator:
xcrun simctl uninstall <UDID> com.example.Agmente
- Optionally shut simulator down if requested.
Preferred Execution
Use the bundled script for deterministic runs:
scripts/run_codex_local_e2e.sh
Managed-server example:
scripts/run_codex_local_e2e.sh \
--endpoint ws://127.0.0.1:8788 \
--udid <SIMULATOR_UDID> \
--start-codex-cmd "codex app-server --listen ws://127.0.0.1:8788"
Existing-server example:
scripts/run_codex_local_e2e.sh \
--endpoint ws://127.0.0.1:8788 \
--udid <SIMULATOR_UDID>
Reporting Requirements
What ships with it
3 files 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.
- 3d ago First seen · 74 lines · 63 tokens per session scan A 27b63860e3c9
codex-local-cli-e2e is a skill published in the GitHub repository rebornix/Agmente (540 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 656 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-30.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
test-conversion
Workflow for converting unit tests to browser tests for Project Bedrock. Invoke this when the user wants to remove complex Browser dependencies from tests.
agui-dotnet-cross-language-tests
Author cross-language interop tests that verify the AG-UI .NET SDK is wire-compatible with the TypeScript SDK — a Vitest TS client driving a C# CrossLanguage.TestServer over HTTP, both directions, including protobuf byte-parity against @ag-ui/proto. USE FOR: adding or modifying cross-language interop coverage…
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.