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 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/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/anombyte93/atlas-session-lifecycle/start"><img src="https://agentmods.dev/badge/skills/anombyte93/atlas-session-lifecycle/start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 374 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 203 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 359 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00055 | $0.04406 |
| Opus 5.5 | $0.00022 | $0.01762 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (85 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 4,406 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
file-organizer
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
digital-brain
This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.
material-organizer
Organize only the materials the user has already provided or explicitly pointed to. The job is to make messy inputs easier to scan, reuse, archive, or continue from later while preserving source traceability.
base
Universal coding patterns, constraints, TDD workflow, atomic todos.
session-management
Context preservation, tiered summarization, resumability.
context-shunt
Offload large / multi-file reads to a cheap worker model so raw files never enter Claude's context (token savings).