spot-drift

spot-drift is a skill for Claude Code from kriscard/Skills. It costs 67 tokens per session (1,406 once invoked), scanned A, original, MIT.

An Obsidian review that compares your stated priorities with how you used your notes over the last 30 days. It highlights neglected goals and possible avoidance.

In plain words
What is it for?
Use it to check whether you are drifting from quarterly or monthly goals, identify neglected projects, and explore what you may be avoiding.
Why use it?
It helps reveal when your daily activity no longer matches what you say matters. It asks for missing context instead of guessing about your intentions.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the skills plugin — 44 skills shipped together

Good fit Use it to check whether you are drifting from quarterly or monthly goals, identify neglected projects, and explore what you may be avoiding.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kriscard/skills/spot-drift
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 kriscard/Skills --skill spot-drift
Clone the repo
git clone --depth 1 https://github.com/kriscard/Skills

Made for: Claude Code.

Or install skills, the plugin that ships this one along with the rest of its 44 skills.

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 spot-drift

README.md
[![agentmods](https://agentmods.dev/badge/skills/kriscard/skills/spot-drift.svg)](https://agentmods.dev/skills/kriscard/skills/spot-drift)
Your own site
<a href="https://agentmods.dev/skills/kriscard/skills/spot-drift"><img src="https://agentmods.dev/badge/skills/kriscard/skills/spot-drift.svg" alt="Measured on agentmods" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,406 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.00067 $0.01406
Opus 5 $0.00034 $0.00703
Sonnet 5 $0.00013 $0.00281
Haiku 4.5 $0.00007 $0.00141

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

Security

Grade A, and why

spot-drift 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 8d 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.

skills/obsidian/spot-drift/SKILL.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spot Drift

Compare stated intentions against actual vault behavior over the past 30 days. Surface the gap between what you say matters and where energy actually goes. Find what's being avoided.

Ask, Don't Assume

Shared principle (canonical version in the vault skill): never guess, deduce, or fill gaps with assumptions about the user's notes, priorities, or intent. If you don't know — a date range, what counts as a win, which goals are active — ask. Before writing any synthesis or judgment into a note, show your draft with its source and get explicit confirmation. Missing data is not permission to invent.

Obsidian Access

Use Obsidian CLI via Bash. On failure: "Obsidian CLI isn't working — update Obsidian with CLI enabled."

Step 1 — Gather Stated Intentions

OKRs and Goals

obsidian files folder="2 - Areas/Goals/Quaterly/" format=json
obsidian files folder="2 - Areas/Goals/Monthly/" format=json
# Read the most recent quarterly and monthly goal notes
obsidian base:query path="2 - Areas/Goals/OKR Dashboard.base" format=json

Extract: stated priorities, self-commitments, items marked important/urgent, open questions flagged for investigation, projects in active/current status.

Daily Note Intentions (past 30 days)

TODAY="2 - Areas/Daily Ops/$(date +%Y)/$(date +%Y-%m-%d).md"   # then read backwards
obsidian read path="2 - Areas/Daily Ops/<year-from-YYYY-MM-DD>/YYYY-MM-DD.md"
obsidian property:read path="2 - Areas/Daily Ops/<year-from-YYYY-MM-DD>/YYYY-MM-DD.md" name="energy_sleep"

Completion: attempt all 30 dates, list missing or sparse notes explicitly, and do not treat gaps as proof of inactivity.

Look for: "I need to..." / "I should..." / "I want to..." statements, carry-forward items from reflections, recurring themes that keep appearing, things flagged as tomorrow's priority that never get done.

Step 2 — Gather Actual Behavior

Vault Activity per Stated Priority

obsidian search:context query="<stated priority A>" format=json limit=10
obsidian search:context query="<stated priority B>" format=json limit=10
obsidian backlinks file="<priority project note>" counts

Read the full file on GitHub · 149 lines

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. 8d ago First seen · 149 lines · 67 tokens per session scan A 5487c790309b

Subscribe to this mod's changes

spot-drift is a skill published in the GitHub repository kriscard/Skills (14 stars, last pushed 27d ago), licensed MIT. It adds 67 tokens to every session and 1,406 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories