re-anchor

re-anchor is a command for Claude Code from goldenwo/claude-state-drift. It costs 52 tokens per session (176 once invoked), scanned A, original, MIT.

A command that checks whether the current work still matches the project's objective stored in .claude/state.json.

In plain words
What is it for?
Use it after extended work, when the scope may have changed, or before declaring a task complete.
Why use it?
Long coding sessions can drift away from the original task; this reports whether that has happened without changing project state.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the claude-state-drift plugin — 3 skills, 6 commands, 4 hooks shipped together

Good fit Use it after extended work, when the scope may have changed, or before declaring a task complete.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/goldenwo/claude-state-drift/re-anchor
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.

Clone the repo
git clone --depth 1 https://github.com/goldenwo/claude-state-drift

Made for: Claude Code.

Or install claude-state-drift, the plugin that ships this one along with the rest of its 3 skills, 6 commands, 4 hooks.

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 re-anchor

README.md
[![agentmods](https://agentmods.dev/badge/commands/goldenwo/claude-state-drift/re-anchor/github.svg)](https://agentmods.dev/commands/goldenwo/claude-state-drift/re-anchor)
Your own site
<a href="https://agentmods.dev/commands/goldenwo/claude-state-drift/re-anchor"><img src="https://agentmods.dev/badge/commands/goldenwo/claude-state-drift/re-anchor/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 re-anchor

Your own site · 80×15
<a href="https://agentmods.dev/commands/goldenwo/claude-state-drift/re-anchor"><img src="https://agentmods.dev/badge/commands/goldenwo/claude-state-drift/re-anchor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 176 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.00052 $0.00176
Opus 5 $0.00026 $0.00088
Sonnet 5 $0.00010 $0.00035
Haiku 4.5 $0.00005 $0.00018

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

Security

Grade A, and why

re-anchor 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 10d 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.

commands/re-anchor.md · 9 lines

What it actually says

Invoke the Skill tool with claude-state-drift:re-anchor against the current project. Do not inline or paraphrase the procedure — defer to the skill for the full contract (objective re-read → recent-work audit → alignment categories on-track/mild/significant → handoff to update-state if needed).

If .claude/state.json doesn't exist in the current project, report that and skip the audit (no enforcement on uninstrumented projects).

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. 10d ago First seen · 9 lines · 52 tokens per session scan A cd41e5284777

Subscribe to this mod's changes

re-anchor is a command published in the GitHub repository goldenwo/claude-state-drift (1 stars, last pushed 23d ago), licensed MIT. It adds 52 tokens to every session and 176 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-31.