What is update-status?

A command for changing the verification state of a node in an EDN proof graph, a structured file that records reasoning steps and their relationships. Available states include proposed, verified, admitted, and rejected.

Use it after reviewing a proof node to mark it verified, admitted, or rejected, or to update its state as part of the proof-review workflow.

It lets reviewers record whether a proof step was accepted, challenged, or temporarily accepted, while updating dependent steps when needed.

How tobiasosborne/alethfeld configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to tobiasosborne/alethfeld. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/tobiasosborne/alethfeld/legacy/.claude/commands/update-status.md

Clone the repo

git clone --depth 1 https://github.com/tobiasosborne/alethfeld

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/tobiasosborne/alethfeld/update-status/github.svg)](https://agentmods.dev/commands/tobiasosborne/alethfeld/update-status)

Your own site

<a href="https://agentmods.dev/commands/tobiasosborne/alethfeld/update-status"><img src="https://agentmods.dev/badge/commands/tobiasosborne/alethfeld/update-status/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/tobiasosborne/alethfeld/update-status"><img src="https://agentmods.dev/badge/commands/tobiasosborne/alethfeld/update-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 452 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.

Model	Per session	Once invoked
Fable 5.1	$0.00008	$0.00452
Opus 5	$0.00004	$0.00226
Sonnet 5	$0.00002	$0.00090
Haiku 4.5	$0.00001	$0.00045

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

Security

Grade A, and why

update-status 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 9d 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.

.claude/commands/update-status.md · 71 lines

What it actually says

Update Node Status

Update the verification status of a node after review by the Verifier.

When to Use

Use this command when:

The Verifier accepts a step: proposed → verified
The Verifier rejects a step: proposed → rejected
A step needs to be admitted: proposed → admitted

Invocation

./cli/scripts/alethfeld update-status <graph.edn> <node-id> <status>

Arguments

<graph.edn> - Path to the proof graph file
<node-id> - The node ID (keyword format, e.g., :1-abc123)
<status> - New status: proposed, verified, admitted, or rejected

Example

./scripts/alethfeld update-status proof.edn :1-abc123 verified

Status Values

Status	Meaning
`proposed`	Initial state, awaiting verification
`verified`	Verifier accepts the step
`admitted`	Temporarily accepted without full verification (creates proof obligation)
`rejected`	Verifier challenges the step (requires revision)

Side Effects

Taint Propagation

Status changes trigger automatic taint recomputation:

:admitted → node becomes :self-admitted, all dependents become :tainted
:verified → depends on ancestor taints
Changes propagate to all transitive dependents

Obligations

Setting status to :admitted adds a proof obligation
Changing from :admitted to another status removes the obligation

Output Format

Success:

{:status :ok
 :message "Node :1-abc123 status updated to verified"
 :graph-version 26}

Options

--dry-run or -d - Validate without writing
--output FILE or -o FILE - Write to different file

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.

9d ago First seen · 71 lines · 8 tokens per session scan A e1aabebe8c20

Subscribe to this mod's changes

update-status is a command published in the GitHub repository tobiasosborne/alethfeld (144 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 452 once invoked, about $0.0000 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.

alethfeld: Command for Claude Code