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-compactgit 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-compact)<a href="https://agentmods.dev/skills/blazity/atlas/atlas-compact"><img src="https://agentmods.dev/badge/skills/blazity/atlas/atlas-compact/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-compact"><img src="https://agentmods.dev/badge/skills/blazity/atlas/atlas-compact.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.00049 | $0.00984 |
| Opus 5.5 | $0.00020 | $0.00394 |
| Sonnet 5.5 | $0.00010 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00098 |
Grade A, and why
atlas-compact 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compact AI Context
Overview
Use this skill when atlas doctor reports context-size advisories or AI-facing context files grow oversized. The published CLI owns deterministic measurement — which files count, their sizes, thresholds, and statuses. This skill owns semantic judgment — what to cut, move, merge, or keep. Never reimplement measurement, guess sizes, or invent thresholds.
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.
This skill edits content only. Structure repair — directories, config, symlinks, managed files — stays with doctor --fix.
Run the phases below in order.
Phase 1 — Deterministic Measurement
From the repository root, run:
npx --no-install @blazity-atlas/core doctor
Follow the result before compacting anything:
- Manual findings (exit 2): summarize the conflicts and stop.
- Fixable drift (exit 1): offer
npx --yes @blazity-atlas/core@latest doctor --fixfirst — structure repair precedes compaction. If--fixrefuses because of a dirty worktree, ask the user whether to commit, stash, or explicitly rerun with--force; never use--forceautomatically. - No context-size advisory and no user-named target: report that the AI context is within thresholds and stop.
Capture the authoritative per-file worklist:
npx --no-install @blazity-atlas/core doctor --handoff context-size
Treat its entry lines as the worklist; do not re-measure by hand.
Phase 2 — Read and Classify
Resolve every path through the workspace config — never hardcode .ai/: read .ai/config.json, or when absent, follow the .atlas repo-root pointer to <root>/config.json.
Read each flagged file and bucket its content:
- Commands, invariants, and safety rules → stay in root instructions.
- Durable product, architecture, stack, and lesson detail → configured memory files.
- Decisions and rationale → configured decisions/ADR paths.
- Canonical terms → the configured language file.
- Duplicated content → keep one canonical location and reference it from the rest.
- Stale content contradicted by the repository (with evidence) → delete.
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 · 77 lines · 49 tokens per session scan A 468185810fb0
atlas-compact is a skill published in the GitHub repository Blazity/atlas (26 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 984 once invoked, about $0.0002 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…