obsidian-tracker-where-was-i

obsidian-tracker-where-was-i is a skill for Claude Code from IvanLutsenko/awac-ai-agent-plugins. It costs 37 tokens per session (427 once invoked), scanned A, original, MIT.

A resume summary for an Obsidian project that shows the last session, active tasks, open bugs, decisions, and a suggested next action. Obsidian is a note-taking application used here to store project records.

In plain words
What is it for?
Use it when returning to a project after a break or switching sessions, especially when you need its recent decisions and unfinished work.
Why use it?
It reduces the time needed to reconstruct where work stopped and what should happen next.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code; mentions Codex.

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

Good fit Use it when returning to a project after a break or switching sessions, especially when you need its recent decisions and unfinished work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ivanlutsenko/awac-ai-agent-plugins/where-was-i
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 where-was-i
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-where-was-i

README.md
[![agentmods](https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/where-was-i/github.svg)](https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/where-was-i)
Your own site
<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/where-was-i"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/where-was-i/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.

agentmods 80×15 button for obsidian-tracker-where-was-i

Your own site · 80×15
<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/where-was-i"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/where-was-i.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 427 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.00037 $0.00427
Opus 5 $0.00018 $0.00214
Sonnet 5 $0.00007 $0.00085
Haiku 4.5 $0.00004 $0.00043

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

Security

Grade A, and why

obsidian-tracker-where-was-i 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.

plugins/obsidian-tracker/skills/generated-from-commands/where-was-i/SKILL.md · 63 lines

What it actually says

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

/where-was-i — Resume Context

Goal

Show the user a compact context block to quickly resume work on a project.

Steps

  1. Determine project:

    • If .claude/obsidian-tracking.json exists, use the project from it.
    • Otherwise, call findProjectByLocalPath with the current working directory.
    • If still no project, call listProjects and ask the user which project.
  2. Get resume context:

    • Call getResumeContext with the resolved project name.
  3. Format output as a compact block:

# Resume Context for {project}

## Current Focus
{suggestedAction}

## Last Session ({date})
Completed:
- {items}

Blockers: {items or "None"}

## Active Work
Tasks:
- [{status}] {title}

Bugs:
- [{priority}] {title}

## Recent Decisions
- {DEC-id}: {title}
  1. Keep it token-efficient:

    • No descriptions, only titles and statuses.
    • Target ~300-500 tokens max.
    • If a section is empty, show "None" on one line, don't skip the section.
  2. If no data exists (no summaries, no tasks, no bugs):

    • Say "No previous session data found for {project}. This looks like a fresh start."
  3. Auto-start tracking: If .claude/obsidian-tracking.json does not exist, start tracking for the resolved project:

    plugins/obsidian-tracker/scripts/start-tracking.sh "{project}"
    
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. 3d ago First seen · 63 lines · 0 tokens per session scan A 81a6db0f0ea7

Subscribe to this mod's changes

obsidian-tracker-where-was-i is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 5d ago), licensed MIT. It adds 37 tokens to every session and 427 once invoked, about $0.0002 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

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

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

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