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/dante01yoon/codex-mcp-bridge/codex-testnpx skills add dante01yoon/codex-mcp-bridge --skill codex-testgit clone --depth 1 https://github.com/dante01yoon/codex-mcp-bridgeWrote 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/dante01yoon/codex-mcp-bridge/codex-test)<a href="https://agentmods.dev/skills/dante01yoon/codex-mcp-bridge/codex-test"><img src="https://agentmods.dev/badge/skills/dante01yoon/codex-mcp-bridge/codex-test.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.00026 | $0.00281 |
| Opus 5 | $0.00013 | $0.00140 |
| Sonnet 5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
Codex Test 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 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.
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
Generate tests for the specified code using Codex as a sub-agent.
Steps
- Read the target file(s) specified in the arguments.
- Detect the project's testing framework by checking existing test files, config, and dependencies.
- Call
mcp__codex-bridge__consult_codex_with_stdinwith:stdin_content: the full content of the target file(s)prompt: "Generate comprehensive unit tests for this code. Include edge cases, error cases, and happy path. Use [FRAMEWORK] as the testing framework. Return only the test code."format: "code"timeout: 180sandbox: "read-only"
- Replace
[FRAMEWORK]with the detected framework (pytest, vitest, jest, etc.). - Write the tests to the appropriate test file location following the project's test structure.
$ARGUMENTS
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 · 30 lines · 26 tokens per session scan A b11bea760357
Codex Test is a skill published in the GitHub repository dante01yoon/codex-mcp-bridge (2 stars, last pushed 6mo ago), licensed MIT. It adds 26 tokens to every session and 281 once invoked, about $0.0001 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 skills, from other repositories
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
add-go-test
Write or extend Go unit tests in this repo. Use when the user asks to add or update Go tests.