Imported from zhuhaow/codex-fixes (AGENTS.md). Install upstream with npx skills add zhuhaow/codex-fixes. Copyright stays with the author.

Codex Fixes Agent Guide

This repository keeps agent-facing project instructions in .agents/skills/.

When creating, reviewing, or running Codex Fixes issue manifests and fix scripts, read:

.agents/skills/fix-development/SKILL.md

Use the skill instructions together with the source files they reference. If those instructions or the registry schema do not answer a product or safety question, ask the project owner before inventing new fields or behavior.

When creating GitHub issues or pull requests for this project, follow the repository templates:

.github/ISSUE_TEMPLATE/
.github/pull_request_template.md

Choose the issue template that matches the work: bug candidate, fix proposal, or upstream fixed. Keep issue and PR content aligned with the template fields, especially public evidence links, supported targets, fix safety, and the relevant validation checklist.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install codex-fixes and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

codex-fixes

About

Codex Fixes Agent Guide

Use it

Install codex-fixes and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews