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/enakoneschniy/claude-dev-stack/session-managernpx skills add Enakoneschniy/claude-dev-stack --skill session-managergit clone --depth 1 https://github.com/Enakoneschniy/claude-dev-stackWhat 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.00108 | $0.02137 |
| Opus 5 | $0.00054 | $0.01069 |
| Sonnet 5 | $0.00022 | $0.00427 |
| Haiku 4.5 | $0.00011 | $0.00214 |
Grade A, and why
session-manager 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 3d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Manager Skill
Context is loaded at SessionStart by
hooks/session-start-context.sh. This skill only handles end-of-session logging (/end) and explicit resume requests (/resume).
Manage development session lifecycle for multi-project work. Eliminates Claude Code "amnesia" by maintaining session logs and project context in an Obsidian vault.
Vault Location
Default: ~/vault/
Override with env var: VAULT_PATH
Commands
/resume
Explicit re-load of project context. The SessionStart hook (hooks/session-start-context.sh)
already loads context at session start — use this command only to force a re-read
mid-session (e.g., after manually editing context.md or after switching projects).
VAULT="${VAULT_PATH:-$HOME/vault}"
PROJECT_NAME=$(basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)")
PROJECT_DIR="$VAULT/projects/$PROJECT_NAME"
CURRENT_DIR=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
# SSR-01: if the SessionStart hook already loaded context <60 min ago,
# skip redundant cat — context is already in the model's prompt.
MARKER="$CURRENT_DIR/.claude/.session-loaded"
if [ -f "$MARKER" ]; then
NOW=$(date +%s)
MTIME=$(stat -f %m "$MARKER" 2>/dev/null || stat -c %Y "$MARKER" 2>/dev/null || echo 0)
AGE=$(( NOW - MTIME ))
if [ "$AGE" -lt 3600 ] && [ "$AGE" -ge 0 ]; then
echo "📋 Context pre-loaded at $(cat "$MARKER" 2>/dev/null) by SessionStart hook — skipping redundant cat."
return 0 2>/dev/null || exit 0
fi
fi
cat "$PROJECT_DIR/context.md" 2>/dev/null || echo "No context.md found for $PROJECT_NAME"
# Last 3 session logs
for f in $(ls -t "$PROJECT_DIR/sessions/"*.md 2>/dev/null | head -3); do
echo "=== $(basename "$f") ==="
cat "$f"
echo ""
done
/end or /done
Create session log and update context.
PROJECT_NAME=$(basename $(git rev-parse --show-toplevel 2>/dev/null || pwd))
VAULT=${VAULT_PATH:-~/vault}
PROJECT_DIR="$VAULT/projects/$PROJECT_NAME"
SESSION_FILE="$PROJECT_DIR/sessions/$(date +%Y-%m-%d)-SESSION_SLUG.md"
# Create session log
cat > "$SESSION_FILE" << 'EOF'
# Session: DATE — DESCRIPTION
## Что сделано
- (list concrete changes: files modified, features added, bugs fixed)
## Решения
- (architectural decisions made, if any)
## TODO на следующую сессию
- [ ] (specific actionable items)
## Проблемы
- (bugs encountered, workarounds used, tech debt noted)
## Изменённые файлы
- (list key files that were modified)
## Зависимости
- (new packages added, version changes)
EOF
# Update context.md "Session History" section (D-01, D-02)
# Invokes the same Node wrapper the Stop hook uses — idempotent by filename.
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
REPO_ROOT="$(cd "$(git rev-parse --show-toplevel 2>/dev/null || pwd)" && pwd)"
UPDATER="$REPO_ROOT/hooks/update-context.mjs"
if [ -f "$UPDATER" ]; then
VAULT_PATH="$VAULT" CDS_PROJECT_NAME="$PROJECT_NAME" \
node "$UPDATER" "$(basename "$SESSION_FILE")" 2>/dev/null || true
fi
# ── Auto-ADR Capture (Phase 26, ADR-02) ────────────────────────
# Scans the session transcript and writes architectural decisions to vault.
# Fail-open: never blocks /end if the bridge errors.
ADR_BRIDGE="$REPO_ROOT/lib/adr-bridge-session.mjs"
if [ -f "$ADR_BRIDGE" ]; then
# SESSION_ID may be substituted by Claude from its runtime context.
# If unset, the bridge falls back to most-recent-mtime JSONL detection.
ADR_RESULT=$(VAULT_PATH="$VAULT" CDS_PROJECT_NAME="$PROJECT_NAME" \
node "$ADR_BRIDGE" \
--session-log "$(basename "$SESSION_FILE")" \
--cwd "$REPO_ROOT" \
${SESSION_ID:+--session-id "$SESSION_ID"} \
2>/dev/null) || ADR_RESULT='{"newAdrs":[],"superseded":[],"error":"bridge failed"}'
# ADR_RESULT is valid JSON: {"newAdrs":[...],"superseded":[...],"error":null|string}
# Claude reads this variable and formats a one-line summary for the user.
echo "$ADR_RESULT"
fi
# ────────────────────────────────────────────────────────────
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.
- 3d ago First seen · 220 lines · 108 tokens per session scan A 6059423c3613
session-manager is a skill published in the GitHub repository Enakoneschniy/claude-dev-stack (5 stars, last pushed 4mo ago), licensed MIT. It adds 108 tokens to every session and 2,137 once invoked, about $0.0005 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-31.
Other skills, from other repositories
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
knowledge-base-management
Obsidian 知识库全生命周期管理:三层架构、素材入库(ABC分级)、健康检查、GBrain/GraphRAG/LLM Wiki 三件套集成、目录整理.
ork-assess
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a request asks to assess, rate, compare, identify trade-offs, evaluate readiness, or decide whether an approach is good enough. Do not use for a full pull-request review or to implement a chosen…
behavior-design
Use when a goal must be converted into a repeatable behavior, cue, SOP, review cadence, and identity-aligned reinforcement.
daily-okr
Use when planning or closing a daily knowledge-compounding cycle across input, cognition, wiki, behavior, creativity, output, and feedback.