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 syncgit 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/sync)<a href="https://agentmods.dev/skills/anombyte93/atlas-session-lifecycle/sync"><img src="https://agentmods.dev/badge/skills/anombyte93/atlas-session-lifecycle/sync/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/sync"><img src="https://agentmods.dev/badge/skills/anombyte93/atlas-session-lifecycle/sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 13 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.
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.00690 |
| Opus 5.5 | $0.00020 | $0.00276 |
| Sonnet 5.5 | $0.00010 | $0.00138 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
sync 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync
Zero questions. Edit files. Print summary. Done.
Rules
- No questions — never ask the user anything. Just save.
- No subagents — run entirely in the main thread.
- No MCP tools — direct file reads and edits only (faster).
- No narration — don't announce steps. Just do them.
- Touch every file — even if only adding a timestamp entry.
- Speed over perfection — a rough sync beats no sync.
Execute
Use the current time formatted as HH:MM DD/MM/YY for the checkpoint header.
1. Edit session-context/CLAUDE-activeContext.md
Append a new section at the end:
## [SYNC] {time}
**Accomplished:**
- {bullet list of what was done this session}
**In progress:**
- {what's currently being worked on}
**Next steps:**
- {what comes next}
**Blockers:**
- {any blockers, or "None"}
2. Edit session-context/CLAUDE-decisions.md
Append new decisions made this session. If none, append:
## {time}
No new decisions this session.
3. Edit session-context/CLAUDE-patterns.md
Append new patterns discovered. If none, append:
## {time}
No new patterns this session.
4. Edit session-context/CLAUDE-troubleshooting.md
Append new issues and solutions. If none, append:
## {time}
No new issues this session.
5. Update MEMORY.md
Update the auto-memory file at the project memory path with any new learnings from this session. If nothing new, skip this file (memory should stay concise).
6. Print summary
Print exactly one block:
Synced. {N} files updated.
- Active context: {1-line summary of what was captured}
- Decisions: {count new or "no new"}
- Patterns: {count new or "no new"}
- Troubleshooting: {count new or "no new"}
- Memory: {updated or "no changes"}
/sync --full (Capability Inventory)
Extended sync that includes capability inventory generation.
Execute
- Run standard sync flow (Steps 1-5 above).
- Call
session_capability_inventory(project_dir, force_refresh=True)— bypasses cache and regenerates inventory even if git unchanged. - If
needs_generation == True: the MCP tool will generate the inventory. - Read
CLAUDE-capability-inventory.mdif it exists.
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 · 114 lines · 49 tokens per session scan A ffd069bfffe2
sync is a skill published in the GitHub repository anombyte93/atlas-session-lifecycle (85 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 690 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
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…
context-fundamentals
This skill should be used when the user asks to "understand context", "explain context windows", "design agent architecture", "debug context issues", "optimize context usage", or discusses context components, attention mechanics, progressive disclosure, or context budgeting. Provides foundational understanding of…
knowledge-steward
A knowledge-management helper that saves useful prompts, solutions, ideas, patterns, and workflow notes to an Obsidian knowledge base. Obsidian is a local app for organizing linked notes.
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.
session-management
Context preservation, tiered summarization, resumability.
code-graph
AST-based code graph for fast symbol lookup, dependency analysis, and blast radius via codebase-memory-mcp MCP server.