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 commands/varienos/agentic-workflow/codex-verify.skeletongit clone --depth 1 https://github.com/varienos/agentic-workflowWhat 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.00000 | $0.01330 |
| Opus 5 | $0.00000 | $0.00665 |
| Sonnet 5 | $0.00000 | $0.00266 |
| Haiku 4.5 | $0.00000 | $0.00133 |
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 2d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Verify — Codex Target Verify/Adapt Pass
Transform sonrasi Codex hedef yuzeyini denetler; ikinci bootstrap yapmaz. Kullanim:
/codex-verify
Amac
Bu komut, /bootstrap ve transform.js sonrasinda Codex hedefinin kullanilabilir olup olmadigini kontrol eder.
Bu bir bootstrap degildir. Manifest, backlog veya Claude canonical ciktilari yeniden uretilmez. Komut yalnizca mevcut manifesti ve Codex target ciktilarini okur; gerekirse sadece Codex hedef yuzeyi icin rapor veya kucuk adaptasyon onerisi hazirlar.
Girisler
- Manifest:
../Docbase/agentic/project-manifest.yaml - Claude canonical kaynak:
.claude/ - Codex target ciktilari:
.agents/skills/*/SKILL.md,AGENTS.md - Yardimci dokumanlar: README, onboarding veya bootstrap tamamlanma raporu
Step 1 — Manifest ve Target Kontrolu
../Docbase/agentic/project-manifest.yamldosyasini oku.manifest.targetsalanini kontrol et.codexhedefi yoksa raporla ve dur:
Codex verify/adapt atlandi: manifest.targets icinde `codex` yok.
Sadece Claude Code hedefi secildiyse transform ve Codex verify/adapt calismaz.
codexhedefi varsa devam et.
Step 2 — Cikti Varlik Kontrolu
Asagidaki dosya ve dizinleri kontrol et:
.agents/skills/.agents/skills/*/SKILL.mdAGENTS.md
Eksikse yeniden bootstrap onerme. Kullaniciya yalnizca transform komutunu oner:
node transform.js ../Docbase/agentic/project-manifest.yaml --targets codex --verbose
Step 3 — Codex Skill Kalite Kontrolu
Her SKILL.md icin sunlari denetle:
- YAML frontmatter var.
namevedescriptionalanlari dolu.- Komut cagirma ornekleri Codex hedefinde
$komutformatina adapte edilmis. .claude/commands/veya.claude/agents/referanslari hedef skill yoluna donusmus..claude/hooks/,.claude/tracking/vesettings.jsongibi Claude-only runtime iddialari Codex hedefinde otomatik calisiyor gibi anlatilmiyor.
Step 4 — AGENTS.md Kontrolu
AGENTS.md icin sunlari denetle:
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.
- 2d 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 (58 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,330 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
status
Show current Craft progress — cycles, stories, backlog in a rich dashboard view.
story-archive
Move a story from a cycle back to the backlog.
project
Manage projects inside a topic wiki. Projects are folders under output/projects/ that group related outputs (playbooks, images, code, data) with a goal captured in WHY.md.
luda
Invoke Luda, your Scrum Master, for board integrity — orphan work items, plan-vs-tracker divergence, Done-without-negative-criteria, parked-without-a-trigger — plus ticket creation and team orchestration.
design-sprint
Orchestrate design-to-implementation workflow for a sprint or feature. Coordinates /ui (Aura) and /fe (Finn).
ledger-plan
Generate implementation plan with backlog, milestones, and test plan constrained by decisions and risks.