helixir: Command for Claude Code

.claude/commands/rea.md

rea is a command for Claude Code from bookedsolidtech/helixir. It costs 20 tokens per session (652 once invoked), scanned A, original, MIT.

A command that reports the current REA session status. REA is a project governance layer that controls how an agent may act.

In plain words
What is it for?
Checking autonomy settings, HALT status, policy profiles, blocked paths, attribution rules, and recent audit entries.
Why use it?
It shows whether the project is frozen, what policy applies, which paths are blocked, and what recent actions were recorded.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is bookedsolidtech/helixir's own configuration. It tells Claude Code how to work on helixir 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 helixir configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bookedsolidtech/helixir. 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/bookedsolidtech/helixir/main/.claude/commands/rea.md
Clone the repo
git clone --depth 1 https://github.com/bookedsolidtech/helixir

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 rea

README.md
[![agentmods](https://agentmods.dev/badge/commands/bookedsolidtech/helixir/rea/github.svg)](https://agentmods.dev/commands/bookedsolidtech/helixir/rea)
Your own site
<a href="https://agentmods.dev/commands/bookedsolidtech/helixir/rea"><img src="https://agentmods.dev/badge/commands/bookedsolidtech/helixir/rea/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 rea

Your own site · 80×15
<a href="https://agentmods.dev/commands/bookedsolidtech/helixir/rea"><img src="https://agentmods.dev/badge/commands/bookedsolidtech/helixir/rea.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 652 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.00020 $0.00652
Opus 5.5 $0.00008 $0.00261
Sonnet 5.5 $0.00004 $0.00130
Haiku 4.5 $0.00002 $0.00065

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

Security

Grade A, and why

rea 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 2mo 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/rea.md · 53 lines

How it starts

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

/rea — Session Status

Prints a concise status overview of the REA governance layer for the current project. Use this at the start of a session, after policy changes, or whenever you need to confirm the runtime posture before acting.

What it reports

  • Autonomy level — current autonomy_level from .rea/policy.yaml (L0–L3) and the max_autonomy_level ceiling
  • HALT status — whether .rea/HALT exists (FROZEN vs. ACTIVE) and, if frozen, the reason
  • Policy profile — the active profile (e.g. bst-internal, client-engagement, minimal)
  • Blocked paths — paths the middleware chain refuses to touch
  • Attribution gating — block_ai_attribution on/off
  • Recent audit entries — last 5 entries from .rea/audit.jsonl with tool name, decision, and timestamp

Behavior

  1. Invoke the CLI: npx rea check
  2. Render the output verbatim — do not interpret, summarize, or add commentary unless the user asks
  3. If .rea/policy.yaml is missing, report: "REA not initialized in this project. Run npx rea init to scaffold."
  4. If .rea/HALT exists, highlight the FROZEN state prominently — the user needs to see this first

Constraints

  • Read-only. This command never writes to .rea/ or any project file.
  • If the CLI is not available (npx rea check fails), report the error and suggest pnpm install or npm install -g @bookedsolid/rea.
  • Never print the contents of audit.jsonl beyond what npx rea check surfaces — the audit log may contain redacted payloads and should be accessed through the CLI, not directly.

Typical output shape

REA Status
  Profile:           bst-internal
  Autonomy:          L1 (ceiling L2)
  HALT:              ACTIVE (unfrozen)
  Attribution gate:  enforced
  Blocked paths:     .env, .env.*, .rea/, node_modules/

Recent audit (last 5):
  2026-04-18T10:42:11Z  Bash              allowed
  2026-04-18T10:41:58Z  Write             allowed
  2026-04-18T10:41:22Z  Edit              denied (blocked-paths)
  2026-04-18T10:40:03Z  mcp__helixir__*   allowed
  2026-04-18T10:39:47Z  Bash              allowed

Read the full file on GitHub · 53 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. 2mo ago First seen · 53 lines · 20 tokens per session scan A e2a4cb38ccca

Subscribe to this mod's changes

rea is a command published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 652 once invoked, about $0.0001 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-08-31.