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 Blazity/atlas --skill atlas-setupgit clone --depth 1 https://github.com/Blazity/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/blazity/atlas/atlas-setup)<a href="https://agentmods.dev/skills/blazity/atlas/atlas-setup"><img src="https://agentmods.dev/badge/skills/blazity/atlas/atlas-setup/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/blazity/atlas/atlas-setup"><img src="https://agentmods.dev/badge/skills/blazity/atlas/atlas-setup.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.00034 | $0.02150 |
| Opus 5.5 | $0.00014 | $0.00860 |
| Sonnet 5.5 | $0.00007 | $0.00430 |
| Haiku 4.5 | $0.00003 | $0.00215 |
Grade A, and why
atlas-setup 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 1mo 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up Atlas
Overview
Use this skill for first setup and later refreshes. The published CLI owns deterministic structure; this skill owns semantic repository understanding.
Humans and agents use the same deterministic entrypoint. Do not reimplement init, doctor, path repair, symlink repair, or managed file repair inside this skill. Call the CLI through npx, preferring a locally installed @blazity-atlas/core (npx --no-install @blazity-atlas/core …) and falling back to the published package only when none is installed. Every npx --yes @blazity-atlas/core@latest … command in this skill is the fallback spelling of that rule, not an instruction to skip the local copy.
Run the phases below in order.
Phase 1 — Deterministic Bootstrap
Before inspecting repository meaning, announce the deterministic setup steps you are about to run.
From the repository root, run the Atlas CLI. Prefer a locally installed copy so the run works offline and matches the version that shipped this skill:
npx --no-install @blazity-atlas/core doctor
Fall back to the published package only when that fails because the package is not installed locally (npx cannot find it — not when doctor itself reports findings):
npx --yes @blazity-atlas/core@latest doctor
If a fix run rewrites files under the workspace skills directory (a newer published version landed), re-read this skill file before continuing.
Then follow the CLI result:
- If Atlas is missing or mostly uninitialized, run
npx --yes @blazity-atlas/core@latest init. - If
doctorreports only fixable drift, runnpx --yes @blazity-atlas/core@latest doctor --fix. - If
doctor --fixrefuses because of a dirty worktree, stop and ask the user whether to commit, stash, or explicitly rerun with--force. Do not use--forceautomatically. - If
doctorreports manual conflicts, summarize those conflicts and stop before semantic setup. - Rerun
npx --yes @blazity-atlas/core@latest doctorafter any init or fix command. - Continue only when
doctorexits clean. Advisory findings (doctorexits 0) do not count as unclean — they are signals this skill resolves in later phases. Only fixable or manual findings block this phase.
What ships with it
1 file 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.
- 1mo ago First seen · 150 lines · 34 tokens per session scan A 7042f1eabe0c
atlas-setup is a skill published in the GitHub repository Blazity/atlas (26 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 2,150 once invoked, about $0.0001 per session on Opus 5.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
aih-refresh
Initialize or refresh repository-local aihaus project memory from verified local evidence.
agent-context-maintainer
Create, update, and validate repository-local AI agent context files such as AGENTS.md, .agents/core.md, .agents/routing.md, provider-specific profiles, and task SKILL.md routing. Use when an AI coding agent (Codex, Claude Code, Gemini, Copilot, Cursor, or others) is asked to make AGENTS.md or SKILL instructions…
memory
Neural memory operations: search stored lessons, store new lessons, inspect memory stats, consolidate episodic patterns, and run decay/pruning.
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory for MiniMax Code. Recall durable context, store important facts and decisions, and link related memories with the mnemon CLI.
durable-session-state
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after compaction or a…