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/ctrl1candv/atlas/skillnpx skills add Ctrl1CandV/Atlas --skill skillgit clone --depth 1 https://github.com/Ctrl1CandV/AtlasWhat 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.00057 | $0.04311 |
| Opus 5 | $0.00028 | $0.02155 |
| Sonnet 5 | $0.00011 | $0.00862 |
| Haiku 4.5 | $0.00006 | $0.00431 |
Grade A, and why
atlas-orchestrate 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 yesterday.
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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atlas workflow orchestration
Atlas 0.1.0 is a local, source-only Windows release. ${ATLAS_HOME} means the user's absolute source root; this document contains no machine-specific path. The observer runs at http://127.0.0.1:8321 after the user starts it.
Use a single model call for simple one-step work. Use Atlas for explicit graph structure, bounded review loops, independent model perspectives, coding-agent worktree changes, or human approval.
Required sequence
- Design YAML with explicit inputs, outputs, routes, and guards.
- Call
atlas_validate_workflow(zero provider calls). - Call
atlas_save_workflowonly when persistence is requested. - Call
atlas_run_workflowwithdry_run: true(zero provider calls and no run directory). - Show unresolved model choices, graph shape, guard limits, agent security boundaries, privacy, and cost implications.
- Call
atlas_run_workflowwithdry_run: falseonly after explicit execution intent. Default is synchronous (wait=true); for long graphs passwait=falseto get arun_idimmediately after preflight instead of blocking the session (mutually exclusive withpersist_as). - Call
atlas_get_runto inspect a created run,atlas_list_runsto page through runs. If and only if its dynamic status isinterrupted, useatlas_resume_run;pausedhuman decisions remain in the local Web UI (which also offers the cancel button for running/waiting runs). To stop a run,atlas_cancel_runrequests cooperative cancellation — the request cannot be revoked; paused/interrupted runs becomecancelleddirectly, and alocal_cliagent execution in flight is terminated with its whole process tree, while SDK-backed model calls finish their current attempt before the next consumption point ends the run.
While a dispatch is in flight, the controller appends node_progress heartbeat events to the run ledger (node/iteration/attempt/model/elapsed_ms/phase; default 30s, run-level via ATLAS_NODE_HEARTBEAT_INTERVAL_S). They prove only that the controller is still waiting — never model-internal progress — and stop before any terminal event, so a long silence after the last heartbeat means the call is still running, not that the stream died.
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.
- yesterday First seen · 127 lines · 57 tokens per session scan A 3583e634fb18
atlas-orchestrate is a skill published in the GitHub repository Ctrl1CandV/Atlas (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 57 tokens to every session and 4,311 once invoked, about $0.0003 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
seller-research
Use when researching a merchant, storefront, marketplace seller, or merchant of record for a buying decision, especially when identity, refund terms, fulfillment, counterfeit risk, domain history, or independent buyer outcomes are uncertain.
product-research
Use when researching or comparing a specific product, model, or variant for a buying decision, especially when specifications conflict, fit or compatibility matters, retailer copy dominates, or the evidence may be incomplete.
agent-discussion
Use when Codex needs read-only external feedback for planning, architecture review, code discussion, strategy review, or decision support.
agent-bug
Register concrete Agent Workbench bug ledger entries with evidence-first records.
algorithmic-art
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright…
bio-strategy
A conversational framework for systematic scientific problem selection, project ideation, troubleshooting, and strategic decision making.