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/wrg32786/aigent-os/codex-adapternpx skills add wrg32786/aigent-os --skill codex-adaptergit clone --depth 1 https://github.com/wrg32786/aigent-osWrote 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/wrg32786/aigent-os/codex-adapter)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/codex-adapter"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/codex-adapter.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.00101 | $0.00882 |
| Opus 5 | $0.00051 | $0.00441 |
| Sonnet 5 | $0.00020 | $0.00176 |
| Haiku 4.5 | $0.00010 | $0.00088 |
Grade A, and why
codex-adapter 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Adapter
This is aigent-OS's first (and currently only) non-Claude executor: a thin wrapper around daemons/codex-adapter.sh that runs a single bounded, mechanical task through the Codex CLI's non-interactive codex exec mode.
Scope -- what "bounded and mechanical" means
Good fits: a scripted rename, a config/gitignore entry, a repetitive multi-file edit with a clear before/after, a lint-fix pass. The task prompt you hand it should be checkable by a human (or you) glancing at the resulting diff -- if you can't describe in one sentence what "done" looks like, it's not bounded enough for this adapter; do it yourself instead.
Not a fit: architecture decisions, anything requiring judgment about tradeoffs, anything touching credentials/secrets/production config, anything the user hasn't explicitly asked to route to Codex.
Before you invoke it
- Confirm the Codex CLI is actually available:
command -v codex(or whateverAIGENT_CODEX_BINis set to). If it isn't installed, tell the user instead of guessing at a path. - State the bounded task in one sentence, and the target directory. If either is unclear, ask -- don't invoke on a guess.
Invocation
bash daemons/codex-adapter.sh "<bounded task prompt>" --dir <path> [--sandbox <mode>]
AIGENT_CODEX_BIN(env, defaultcodex) -- path or name of the Codex CLI binary. Never hardcode a machine-specific path in the invocation; set the env var if the binary isn't onPATH.--dir <path>-- working directory the task runs in. Default: current directory.--sandbox <mode>-- passed through tocodex exec --sandbox. Defaultworkspace-write(Codex may read/write inside--dir, nothing wider).
Example:
AIGENT_CODEX_BIN=codex bash daemons/codex-adapter.sh \
"Add a .gitignore entry for *.tmp files" --dir .
After it runs -- the review gate
The adapter never commits or pushes. It writes:
.aigent/codex-runs/<timestamp>/output.log-- the raw Codex CLI transcript.aigent/codex-runs/<timestamp>/review.diff-- a working-tree diff (tracked changes + a synthetic diff for any new untracked files) if--diris a git repository.aigent/codex-runs/<timestamp>/status.txt--git status --porcelainfor the same tree
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 · 60 lines · 101 tokens per session scan A d5478869faf6
codex-adapter is a skill published in the GitHub repository wrg32786/aigent-os (17 stars, last pushed yesterday), licensed MIT. It adds 101 tokens to every session and 882 once invoked, about $0.0005 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-09-01.
Other skills, from other repositories
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-quick-batch
Batch several /gsd:quick-shaped tasks together — planned, dispatched, and merged as one run.
commit-with-reflection
Git提交与调试反思报告生成技能。用于分析开发过程中的错误、调试步骤和解决方案,生成结构化的中文反思报告,并创建包含报告引用的Git提交。显式请求词:反思提交、智能提交、生成调试报告、commit with reflection。.
gsd-audit-fix
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit.
gsd-pause-work
Create context handoff when pausing work mid-phase.