Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/varienos/agentic-workflownpx agentmods add commands/varienos/agentic-workflow/codex-verify.skeletonWrote 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/commands/varienos/agentic-workflow/codex-verify.skeleton)<a href="https://agentmods.dev/commands/varienos/agentic-workflow/codex-verify.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/codex-verify.skeleton/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/varienos/agentic-workflow/codex-verify.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/codex-verify.skeleton.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01111 |
| Opus 5.5 | $0.00000 | $0.00444 |
| Sonnet 5.5 | $0.00000 | $0.00222 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
codex-verify.skeleton 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 25d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Verify — Codex Target Verify/Adapt Pass
After transform, audits the Codex target surface; does not run a second bootstrap. Usage:
/codex-verify
Purpose
This command checks whether the Codex target is usable after /bootstrap and transform.js.
This is not a bootstrap. Manifest, backlog, or Claude canonical outputs are not regenerated. The command only reads the existing manifest and Codex target outputs; if needed it prepares a report or a small adaptation suggestion for the Codex target surface only.
Inputs
- Manifest:
../Docbase/agentic/project-manifest.yaml - Claude canonical source:
.claude/ - Codex target outputs:
.agents/skills/*/SKILL.md,AGENTS.md - Supporting docs: README, onboarding, or bootstrap completion report
Step 1 — Manifest and Target Check
- Read
../Docbase/agentic/project-manifest.yaml. - Check the
manifest.targetsfield. - If the
codextarget is missing, report and stop:
Codex verify/adapt skipped: `codex` is not in manifest.targets.
If only the Claude Code target was selected, transform and Codex verify/adapt do not run.
- If the
codextarget exists, continue.
Step 2 — Output Existence Check
Check these files and directories:
.agents/skills/.agents/skills/*/SKILL.mdAGENTS.md
If missing, do not suggest re-bootstrap. Suggest only the transform command:
node transform.js ../Docbase/agentic/project-manifest.yaml --targets codex --verbose
Step 3 — Codex Skill Quality Check
For each SKILL.md, audit:
- YAML frontmatter exists.
nameanddescriptionfields are filled.- Command invoke examples are adapted to
$commandformat for the Codex target. .claude/commands/or.claude/agents/references have been converted to the target skill path.- Claude-only runtime claims such as
.claude/hooks/,.claude/tracking/, andsettings.jsonare not described as running automatically on the Codex target.
Step 4 — AGENTS.md Check
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.
- 25d ago Changed · -1 lines 741f287ee36b
- 1mo ago First seen · 109 lines · 0 tokens per session scan A 6cbe06dcdeb3
codex-verify.skeleton is a command published in the GitHub repository varienos/agentic-workflow (59 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,111 tokens. 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 commands, from other repositories
review-pr
PR review using parallel specialized agents for code quality, security, testing, architecture, and performance analysis. Synthesizes findings into a review report with conventional comments (praise/issue/suggestion/nitpick) and approve or request-changes verdict. Use when reviewing pull requests, conducting security…
gh-security-review
Use to perform a dedicated security review of current branch changes before pushing.
fe
Invoke Frontend Developer for React, TypeScript, Next.js, and React Native development.
rev
Invoke Code Reviewer for code quality, security, requirements validation, and best practices review.
mkt
Invoke Marketing Strategist for go-to-market strategy, positioning, and growth.
arch
Invoke Solution Architect for system design, architecture decisions, patterns, and ADRs.