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/webisitystudio/claude-codex-mcp-bridge/ask-codexnpx skills add WebisityStudio/claude-codex-mcp-bridge --skill ask-codexgit clone --depth 1 https://github.com/WebisityStudio/claude-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/webisitystudio/claude-codex-mcp-bridge/ask-codex)<a href="https://agentmods.dev/skills/webisitystudio/claude-codex-mcp-bridge/ask-codex"><img src="https://agentmods.dev/badge/skills/webisitystudio/claude-codex-mcp-bridge/ask-codex.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.1 | $0.00025 | $0.00191 |
| Opus 5 | $0.00013 | $0.00096 |
| Sonnet 5 | $0.00005 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
ask-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 5d 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
Ask Codex
Use the ask_codex MCP tool for the user's request.
- Resolve the current project to an absolute path.
- Pass the user's task in
requestwithout diluting its acceptance criteria. - Keep
useWorktree: truefor implementation work. Usefalseonly when the user explicitly wants work in the current checkout. - If Codex returns
waiting_for_fable, answer the question and continue withbridge_continue_codexusing the returned run ID. - Report changed files and real verification evidence.
- Do not commit, push, merge, deploy, publish, send externally, alter credentials, delete data, or mutate production without explicit approval.
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.
- 5d ago First seen · 18 lines · 25 tokens per session scan A 087830eaac52
ask-codex is a skill published in the GitHub repository WebisityStudio/claude-codex-mcp-bridge (1 stars, last pushed 27d ago), licensed MIT. It adds 25 tokens to every session and 191 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
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.