obsidian-tracker-session-log

obsidian-tracker-session-log is a skill for Claude Code from IvanLutsenko/awac-ai-agent-plugins. It costs 25 tokens per session (525 once invoked), scanned A, original, MIT.

A session-log command that saves a summary of coding work to an Obsidian project. It records the goal, actions, results, and next steps, using active tracking data when available.

In plain words
What is it for?
Use it to document what a session achieved, what remains, and which operations were performed for a selected project.
Why use it?
It removes the need to write a session report from scratch or rely on memory after work is finished.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the AskUserQuestion tool; mentions Claude Code; mentions Codex.

Part of the obsidian-tracker plugin — 19 skills, 19 commands shipped together

Good fit Use it to document what a session achieved, what remains, and which operations were performed for a selected project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ivanlutsenko/awac-ai-agent-plugins/session-log
Install

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.

Any agent
npx skills add IvanLutsenko/awac-ai-agent-plugins --skill session-log
Clone the repo
git clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-plugins

Made for: Claude Code.

Or install obsidian-tracker, the plugin that ships this one along with the rest of its 19 skills, 19 commands.

Wrote 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.

agentmods badge for obsidian-tracker-session-log

README.md
[![agentmods](https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/session-log.svg)](https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/session-log)
Your own site
<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/session-log"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/session-log.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 525 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00525
Opus 5 $0.00013 $0.00262
Sonnet 5 $0.00005 $0.00105
Haiku 4.5 $0.00003 $0.00052

Measured 2d ago against content hash 3e49a0b0c738, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

obsidian-tracker-session-log 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 2d 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.

plugins/obsidian-tracker/skills/generated-from-commands/session-log/SKILL.md · 81 lines

What it actually says

Converted from Claude Code command /session-log. Review and adapt: hooks and MCP tool IDs may need manual mapping for Codex.

Session Log Command

Logs the current Claude Code session to the specified project.

Step 0: Check Configuration

Вызови MCP tool:

mcp__plugin_obsidian_tracker_obsidian__getConfig

Если initialized: false: выполни инициализацию как в /projects команде.

Arguments

  • project-name (optional) - Project to log session to

Logic

  1. Resolve project:

    Если project-name не указан:

    mcp__plugin_obsidian_tracker_obsidian__listProjects
    

    Покажи нумерованный список:

    # Project Status
    1 name Active

    Пользователь может ввести номер или имя проекта.

  2. Collect session info:

    Сначала проверь .claude/obsidian-tracking.json:

    • Если файл существует — используй данные из него (project, goal, actions)
    • Если goal пустой — сгенерируй из контекста разговора
    • Добавь недостающие actions из контекста

    Если файла нет:

    • Goal: Summarize main topic from conversation
    • Actions: List key tool calls and operations

    Всегда спрашивай:

    • Results: What was achieved
    • Next steps: Ask user via AskUserQuestion
  3. Create session via MCP:

    mcp__plugin_obsidian_tracker_obsidian__addSession
    с параметрами:
      project = project name
      goal = session goal
      actions = ["action1", "action2", ...]
      results = what was achieved
      nextSteps = next steps
    
  4. Output:

    📝 Session logged to "{project}"
    📁 Path: {path}
    
    Summary:
    - Goal: {goal}
    - Actions: {count} recorded
    - Next: {nextSteps}
    
  5. Cleanup tracking: Удали .claude/obsidian-tracking.json после успешного логирования.

Changes

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.

  1. 2d ago First seen · 81 lines · 25 tokens per session scan A 3e49a0b0c738

Subscribe to this mod's changes

obsidian-tracker-session-log is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 4d ago), licensed MIT. It adds 25 tokens to every session and 525 once invoked, about $0.0001 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-09-05.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens