oxygen: Command for Claude Code

.claude/commands/accept-agentic-healing.md

accept-agentic-healing is a command for Claude Code from oxy-hq/oxygen. It costs 38 tokens per session (1,435 once invoked), scanned A, original, Apache-2.0.

A command for approving reviewed recordings that update an automated browser-flow test. It moves staged healing data into the test's main recording file and shows the resulting change.

In plain words
What is it for?
Use it after a test repair has been classified as a staged heal. Review the selector changes, run the command for the flow, inspect the diff, and commit the accepted update.
Why use it?
When a test's page selectors change, the command gives you a controlled way to accept the proposed update instead of changing the test silently. It also warns when there is nothing staged to approve.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

This is oxy-hq/oxygen's own configuration. It tells Claude Code how to work on oxygen itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything oxygen configures →

Reuse

Borrowing it

Nothing to install: this file belongs to oxy-hq/oxygen. 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/oxy-hq/oxygen/main/.claude/commands/accept-agentic-healing.md
Clone the repo
git clone --depth 1 https://github.com/oxy-hq/oxygen

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.

agentmods badge for accept-agentic-healing

README.md
[![agentmods](https://agentmods.dev/badge/commands/oxy-hq/oxygen/accept-agentic-healing/github.svg)](https://agentmods.dev/commands/oxy-hq/oxygen/accept-agentic-healing)
Your own site
<a href="https://agentmods.dev/commands/oxy-hq/oxygen/accept-agentic-healing"><img src="https://agentmods.dev/badge/commands/oxy-hq/oxygen/accept-agentic-healing/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 accept-agentic-healing

Your own site · 80×15
<a href="https://agentmods.dev/commands/oxy-hq/oxygen/accept-agentic-healing"><img src="https://agentmods.dev/badge/commands/oxy-hq/oxygen/accept-agentic-healing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,435 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.00038 $0.01435
Opus 5.5 $0.00015 $0.00574
Sonnet 5.5 $0.00008 $0.00287
Haiku 4.5 $0.00004 $0.00144

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

Security

Grade A, and why

accept-agentic-healing 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.

.claude/commands/accept-agentic-healing.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.

Accept staged healing recordings for a flow

Thin wrapper around the runner's --accept-healing subcommand. Promotes staged Tier-2 healing recordings from .cache/healing-staging.json into the main .cache/bespoke-actions.json, shows the resulting diff, and reminds the dev to commit it.

$ARGUMENTS is the flow stem (e.g. chat-ask, builder-edits-app).

Use this only when /fix-agentic-test classified the failure as Tier-2 (staged heal). Running --accept-healing against an empty staging file is a no-op; running it against a staged recording the dev hasn't reviewed is a foot-gun (the new selectors become the test's ground truth without human review).

This command must be run from the root of an oxy-hq/oxygen-internal checkout.

Steps

1. Sanity-check

test -f web-app/tests/agentic/README.md || { echo "Not in an oxy-hq/oxygen-internal checkout"; exit 2; }

2. Confirm there's something to promote

STAGING=web-app/tests/agentic/.cache/healing-staging.json
test -s "$STAGING" || {
  echo "No staged healing entries at $STAGING. Nothing to promote."
  echo "If you expected staged entries, the previous run probably didn't trigger a Tier-2 heal — re-run the flow with /run-agentic-tests first."
  exit 0
}

3. Show what's about to be promoted

echo "=== Staged healing entries ==="
cat "$STAGING" | jq '.entries[] | {flow, case, step_index, staged_at, action_count: (.actions | length)}'

If the staged set targets a different flow than $ARGUMENTS, surface that. The --accept-healing <flow> filter only promotes entries whose flow field matches; others stay staged.

4. (Optional) Open the trace for visual confirmation

If the dev wants to confirm the new selectors hit the right element, the trace from the redrive run is at:

ls -t web-app/tests/agentic/.traces/<flow-stem>-*.zip 2>/dev/null | head -1
pnpm exec playwright show-trace web-app/tests/agentic/.traces/<flow>-<case>.zip

Frame-by-frame DOM, network, screenshots — same debugging tools as a hand-written Playwright suite.

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. 2d ago First seen · 149 lines · 38 tokens per session scan A dd3a1d6ea345

Subscribe to this mod's changes

accept-agentic-healing is a command published in the GitHub repository oxy-hq/oxygen (203 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 1,435 once invoked, about $0.0002 per session on Opus 5.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-10-14.