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 SW-in-beta/simon-skills --skill simon-sessionsgit clone --depth 1 https://github.com/SW-in-beta/simon-skillsWrote 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/sw-in-beta/simon-skills/simon-sessions)<a href="https://agentmods.dev/skills/sw-in-beta/simon-skills/simon-sessions"><img src="https://agentmods.dev/badge/skills/sw-in-beta/simon-skills/simon-sessions/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/sw-in-beta/simon-skills/simon-sessions"><img src="https://agentmods.dev/badge/skills/sw-in-beta/simon-skills/simon-sessions.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.00153 | $0.02203 |
| Opus 5.5 | $0.00061 | $0.00881 |
| Sonnet 5.5 | $0.00031 | $0.00441 |
| Haiku 4.5 | $0.00015 | $0.00220 |
Grade A, and why
simon-sessions 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 2mo 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
simon Sessions
도구 제한: 이 스킬은 세션 관리용이다. 프로젝트 소스 코드를 Edit/Write하지 않는다. 세션 메타데이터 파일만 수정한다.
작업 세션 관리 스킬. **Git 이력을 1차 소스(SSoT)**로 활용하여 작업 현황을 파악하고 이전 작업을 대화형으로 재개합니다.
Why: Git 이력을 SSoT로 사용하는 이유 — 워크트리는 삭제될 수 있고 메모리 파일은 불완전할 수 있지만, 커밋 히스토리는 영구적이기 때문이다. 어떤 소스가 유실되더라도 git log만 있으면 작업 흐름을 재구성할 수 있다.
Why: 다층 소스 스캔 이유 — 단일 소스(예: 워크트리만)에 의존하면 삭제된 워크트리의 세션을 놓치고, 메모리 파일만 보면 커밋되지 않은 작업을 놓치기 때문이다. 워크트리·브랜치·메모리 파일·git 이력을 모두 스캔해야 누락 없이 세션을 탐지할 수 있다.
Instructions
스크립트 경로: ~/.claude/skills/simon-dev/workflow/scripts/manage-sessions.sh
Shared Protocols:
~/.claude/skills/_shared/preamble.md읽기 — Session Isolation, Error Resilience, Forbidden Rules, Agent Teams, Cognitive Independence 공통 프로토콜 포함.
Session Isolation Protocol (확장 — Sessions 전용)
Why: 홈 디렉토리에 격리하는 이유 — 프로젝트 디렉토리에 저장하면 git에 의도치 않게 포함되거나, worktree 삭제 시 세션 데이터가 함께 사라지기 때문이다. 홈 디렉토리의 고정 경로에 격리하면 워크트리 생명주기와 무관하게 세션 데이터가 보존된다.
세션 탐지 시 아래 두 곳을 모두 스캔해야 한다:
세션 데이터 위치:
PROJECT_SLUG=$(git rev-parse --show-toplevel | tr '/' '-')
SESSIONS_DIR="${HOME}/.claude/projects/${PROJECT_SLUG}/sessions"
세션 디렉토리 구조:
~/.claude/projects/{project-slug}/sessions/
├── feat-add-auth/ # simon 세션 (branch name)
│ └── memory/
├── feat-add-db/ # simon 세션 (branch name)
│ └── memory/
├── pm-20260313-143000/ # simon-pm 세션 (timestamp)
│ └── pm/
└── company-20260313-150000/ # simon-company 세션 (timestamp)
└── company/
호환성: 기존 프로젝트 디렉토리의 .claude/memory/, .claude/pm/, .claude/company/도 fallback으로 스캔한다 (마이그레이션 전 세션 지원).
명령 판별
| 의도 | 키워드 | 실행 |
|---|---|---|
| 작업 현황 | "목록", "list", "현황", "어디까지", "뭐 하고 있었지", args 없음 | list flow |
| 세션 검색 | "검색", "search", "찾기", 키워드 언급 | search {keyword} |
| 세션 상세 | "정보", "info", "상세", 브랜치명 언급 | info {branch} |
| 세션 삭제 | "삭제", "delete", "제거", "정리" | delete {branch} |
| 이어서 작업 | "이어서", "continue", "resume", "피드백" | resume flow |
| PR 생성 | "PR", "풀리퀘스트", "push" | pr flow |
list - 작업 현황
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.
- 2mo ago First seen · 153 lines · 153 tokens per session scan A b13b01b4fff3
simon-sessions is a skill published in the GitHub repository SW-in-beta/simon-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 153 tokens to every session and 2,203 once invoked, about $0.0006 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-31.
Other skills, from other repositories
git-ai-search
Search and restore AI conversation context from git history.
remember
Save the decisions, facts, dead ends and architecture this conversation established to Atlas's shared memory, so other agents and future sessions can build on them.
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.
recall-rationale
Recall why a past change was made by locating the Claude Code transcript that produced it. Use when the user asks to "recall the rationale", "find the rationale", "look up the rationale", "why did I do X", "why did we do X", "why was this changed", or "find the transcript for this commit".
release-finalizer
Merges a release PR, associates it with resolved issues, replies to issue reporters, and closes issues. Use after PR review is complete and ready for merge. Closes the release cycle.