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/anombyte93/atlas-session-lifecycle/startnpx skills add anombyte93/atlas-session-lifecycle --skill startgit clone --depth 1 https://github.com/anombyte93/atlas-session-lifecycleWrote 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/anombyte93/atlas-session-lifecycle/start)<a href="https://agentmods.dev/skills/anombyte93/atlas-session-lifecycle/start"><img src="https://agentmods.dev/badge/skills/anombyte93/atlas-session-lifecycle/start.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.00055 | $0.04406 |
| Opus 5 | $0.00028 | $0.02203 |
| Sonnet 5 | $0.00011 | $0.00881 |
| Haiku 4.5 | $0.00006 | $0.00441 |
Grade A, and why
start 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 4d 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 — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Init & Lifecycle Skill
User runs
/start. Questions upfront. Everything else silent. Then seamlessly continue working.
All session operations use atlas-session MCP tools directly (prefixed session_* and contract_*). Use ToolSearch to discover them.
Directive Capture
Capture any text after /start as DIRECTIVE. If empty, the soul purpose is the directive.
The skill NEVER finishes with "ready to go" and stops. After setup, immediately begin working.
UX Contract (MANDATORY)
- NEVER announce step names — no "Init Step 1", no "Wave 2"
- NEVER narrate internal process — no "Detecting environment..."
- NEVER explain what you're about to do — just ask questions, then do it silently
- User sees ONLY: questions and seamless continuation into work
- Batch questions — as few rounds as possible
- No "done" message that stops — after setup, immediately begin working
Hard Invariants
- User authority is absolute — AI NEVER closes a soul purpose. Only suggests; user decides.
- Zero unsolicited behavior — Skill ONLY runs when user types
/start. - Human-visible memory only — All state lives in files.
- Idempotent — Safe to run multiple times.
- Templates are immutable — NEVER edit bundled template files.
- NEVER auto-invoke doubt agent. Only offer it.
- Trust separation — for bounty verify, spawn a separate finality Task agent. Never the same agent that submits.
- AtlasCoin is optional — if the service is down, tell the user and continue without bounty tracking.
Service Availability (MANDATORY)
- NEVER run
claude mcp list— assume atlas-session is available, handle errors on first call - NEVER block on external services — log the gap and continue with degraded mode
- Fallback hierarchy: try tool → if error/timeout → tell user what's degraded → continue
| Service | If Unavailable | Action |
|---|---|---|
| atlas-session MCP | session_start errors/times out |
STOP — required for /start |
| AtlasCoin | contract_health() fails |
Continue without bounty tracking |
| Perplexity | Research queries fail | Context7 + WebSearch fallback |
| Context7 | Doc queries fail | Perplexity results only |
| Bitwarden | Vault locked/unavailable | Tell user, skip credential fetch |
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.
- 4d ago First seen · 388 lines · 55 tokens per session scan A 82a5592f06e8
start is a skill published in the GitHub repository anombyte93/atlas-session-lifecycle (88 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 4,406 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-30.
Other skills, from other repositories
session-orchestrator
Session orchestrator on top of the recall index of all Claude Code sessions: finds a past session by task description, dives in (context, project, skill, artifacts) and acts in one of three modes — finish here, hand off the resume command, or open the session in a new terminal window. Use when user asks: "find the…
vibe-research
Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".
trellis-brainstorm
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex…
trellis-session-insight
Reach into past AI conversation history through the trellis mem CLI. Use whenever the user asks 'how did we solve X last time', 'have we discussed this before', 'what was the decision on X', 'remind me what we did in this task', '上次怎么解的', '之前讨论过吗', '想起一段对话', or when starting a brainstorm that overlaps prior work…
trellis-channel
Use Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.
kn-research
Use when you need to understand existing code, find patterns, search project knowledge, investigate current external facts, or explore a large codebase before implementation.