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 skills add jscraik/Agent-Skills --skill codex-automation-architectgit clone --depth 1 https://github.com/jscraik/Agent-SkillsWrote 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/jscraik/agent-skills/codex-automation-architect)<a href="https://agentmods.dev/skills/jscraik/agent-skills/codex-automation-architect"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/codex-automation-architect/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/skills/jscraik/agent-skills/codex-automation-architect"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/codex-automation-architect.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.00035 | $0.01200 |
| Opus 5 | $0.00017 | $0.00600 |
| Sonnet 5 | $0.00007 | $0.00240 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
codex-automation-architect 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 8d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Automation Architect
Philosophy
- Keep the skill focused on the decision and workflow the user actually requested.
- Preserve important context through progressive disclosure instead of trimming it away.
- Prefer repo-local contracts, wrappers, and validation before generic advice.
When To Use
- The user wants a recurring Codex automation designed, audited, or consolidated.
- A background workflow needs scope, schedule, sandbox, and validation decisions.
- Existing automations need risk review or deduplication.
Avoid
- One-off manual tasks that do not need recurring automation.
- Generic CI setup that belongs to CI-specific skills.
- Automations that lack a safe project path or owner.
Inputs
- automation goal
- target project path
- schedule or trigger
- sandbox posture
- validation and rollback expectations
- existing automation ids or
$CODEX_HOME/automations/*/automation.tomlevidence - Codex app dynamic tool availability (
automation_updateandautomation_list, possibly deferred behindtool_search)
Outputs
- automation design
- risk and scope review
- preflight plan
- validation evidence
- rollout or consolidation notes
- Schema-bound outputs include schema_version.
Workflow
- Start with 2-3 focused surfaces before expanding scope.
- Confirm the automation goal and whether it should be recurring at all.
- Resolve existing automations first by id, name, prompt, and local TOML evidence; prefer update or consolidation over duplicate creation.
- Map kind (
cronorheartbeat), destination, project path, execution environment, permissions, schedule, and expected outputs. - Prefer heartbeats for current-thread follow-ups, especially short delays; prefer cron for detached workspace jobs.
- Use suggested create/update when proposing worktree automations with a non-null local environment setup config so the user can review before save.
- Define preflight, stop conditions, observability, and rollback.
- Validate the final plan or config with repo checks and the Codex app automation tool response.
What ships with it
5 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.
- 8d ago First seen · 118 lines · 35 tokens per session scan A 9021c11ad1bb
codex-automation-architect is a skill published in the GitHub repository jscraik/Agent-Skills (8 stars, last pushed 10d ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,200 once invoked, about $0.0002 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-03.
Other skills, from other repositories
ad-creative
Plan and produce advertising concepts, copy variants, visual directions, and test matrices for paid campaigns.
humanizer-zh
Revise Chinese text to sound specific, fluent, restrained, and human while preserving facts and author intent.
skill-creator
Design and write concise reusable KunAgent skills with valid triggers, real tools, and testable completion criteria.
daily-brief
Produce a dated, source-linked daily brief with prioritized developments, implications, and watch items.
imf-data
Retrieve and analyze IMF macroeconomic series, forecasts, and reserve-composition data.
scholar-research
Search, screen, synthesize, and cite scholarly literature and author metadata.