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/chronoaiproject/nyxid/aevatar-codex-exec-workflow-samplenpx skills add ChronoAIProject/NyxID --skill aevatar-codex-exec-workflow-samplegit clone --depth 1 https://github.com/ChronoAIProject/NyxIDWrote 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/chronoaiproject/nyxid/aevatar-codex-exec-workflow-sample)<a href="https://agentmods.dev/skills/chronoaiproject/nyxid/aevatar-codex-exec-workflow-sample"><img src="https://agentmods.dev/badge/skills/chronoaiproject/nyxid/aevatar-codex-exec-workflow-sample.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.00086 | $0.01883 |
| Opus 5 | $0.00043 | $0.00941 |
| Sonnet 5 | $0.00017 | $0.00377 |
| Haiku 4.5 | $0.00009 | $0.00188 |
Grade A, and why
aevatar-codex-exec-workflow-sample 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 4d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Aevatar codex_exec
Choose exactly one proof
Mount this skill from Ornn and run one bundled workflow for the configured target:
codex-exec-check: canonical managed chrono-sandbox/gVisor proof with no caller routing.codex-exec-private-ssh-check: private NyxID node-backed SSH proof with only service and principal routing.
Configuration, health, UserService, node-online, and direct SDK/SSH checks are prerequisites, not completion evidence. Report codex_exec as usable only after the selected Aevatar workflow returns exact CODEX_EXEC_READY under that target's result contract.
Guardrails
- Fetch the public skill from Ornn. Do not validate only a local workflow copy.
- Keep the fixed probe prompt. Do not replace it with a real task.
- Never place tokens, keys,
auth.json,CODEX_HOME, local paths, model flags, images, providers, or sandbox flags in workflow input. - Do not mix target fields. Managed requires
target.kind=managed_sandboxplusworkspace.kind=empty_git; private requires nestedtarget.private_sshand no workspace. - Managed callers cannot choose a repository, workspace path, image, model, provider, credential, shell, Codex profile, approval policy, or sandbox flags.
- Run through Aevatar as the native NyxID account being verified. Never pass a raw token. Before
the managed proof, use the explicit authenticated credential lifecycle:
POST /api/managed-codex/credential, thenGET /api/managed-codex/credential. Continue only whenexecution_ready=trueandexecution_readiness_reason=ready;status=activealone is insufficient. - Normal
codex_execexecution is credential-read-only. It never provisions, reconciles, rotates, repairs, or retries credentials.
Mount
Call use_skill with workflow mounting enabled:
{
"skill": "aevatar-codex-exec-workflow-sample",
"mount_workflows": true
}
Wait for the mount command to be accepted. Read-model visibility can propagate asynchronously. If mounting is unavailable, fetch this exact public Ornn version and submit the corresponding YAML under assets/ as explicit inline draft-run input; state clearly that it was an inline run.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 170 lines · 86 tokens per session scan A a3fa07be80bd
aevatar-codex-exec-workflow-sample is a skill published in the GitHub repository ChronoAIProject/NyxID (36 stars, last pushed today), licensed Apache-2.0. It adds 86 tokens to every session and 1,883 once invoked, about $0.0004 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-30.
Other skills, from other repositories
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.