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/sasly2048/codex-atlas/syncnpx skills add sasly2048/codex-atlas --skill syncgit clone --depth 1 https://github.com/sasly2048/codex-atlasWrote 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/sasly2048/codex-atlas/sync)<a href="https://agentmods.dev/skills/sasly2048/codex-atlas/sync"><img src="https://agentmods.dev/badge/skills/sasly2048/codex-atlas/sync.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.00020 | $0.00073 |
| Opus 5 | $0.00010 | $0.00036 |
| Sonnet 5 | $0.00004 | $0.00015 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
sync 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.
What it actually says
Run cc-atlas sync and report its output to the user — files ingested,
sessions and tool calls upserted, and any git commits synced.
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 · 9 lines · 20 tokens per session scan A ca3e0489da3e
sync is a skill published in the GitHub repository sasly2048/codex-atlas (1 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 73 once invoked, about $0.0001 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-31.
Other skills, from other repositories
prewalk
Use when the user wants a coding task executed with a strong planner model first and a faster/cheaper executor model after the first successful implementation edit.
cinematic-storyboard-sheet
Generate professional Hollywood-caliber vertical storyboard sheet images from cinematic storyboard text, shot lists, scripts, or character reference images. Use when Codex must call imagegen to create an image-only black-background storyboard layout with 3:2 cinematic frames on the left, aligned production text on the…
deconstruct-bias-dialogue
Guided bias-deconstruction dialogue that combines Madhyamaka catuskoti, phenomenological epoche, Socratic elenchus, and Popperian falsification into progressive questions. Use when the user asks to examine assumptions, biases, beliefs, polarizing claims, identity or group judgments, ethical or political disputes…
pixel-office
Show Codex subagents working in a live Stardew-style pixel office web page. Use PROACTIVELY and implicitly whenever a task starts or observes subagents (spawnagent/collaboration or subagentactivity), even when the user never mentions this plugin; automatically open the Codex app right sidebar page. Also use when the…
manage-taskboard
Manage Codex Taskboard / e-taskboard work with taskctl. Use for taskboard issue IDs, status sync, comments, or taskctl cloud setup—not for unrelated product docs.
dev-flow
Use Dev Flow for bounded Codex software development tasks: implementation, bug fixes, refactoring, targeted testing, development delivery, and explicit parallel batches isolated in separate Git worktrees. It may be selected implicitly for those tasks or explicitly with $dev-flow-codex:dev-flow. Do not create a Dev…