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.
npx agentmods add commands/bookedsolidtech/helixir/reagit clone --depth 1 https://github.com/bookedsolidtech/helixirWhat 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 | $0.00020 | $0.00652 |
| Opus 5 | $0.00010 | $0.00326 |
| Sonnet 5 | $0.00004 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
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 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.
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_levelfrom.rea/policy.yaml(L0–L3) and themax_autonomy_levelceiling - HALT status — whether
.rea/HALTexists (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_attributionon/off - Recent audit entries — last 5 entries from
.rea/audit.jsonlwith tool name, decision, and timestamp
Behavior
- Invoke the CLI:
npx rea check - Render the output verbatim — do not interpret, summarize, or add commentary unless the user asks
- If
.rea/policy.yamlis missing, report: "REA not initialized in this project. Runnpx rea initto scaffold." - If
.rea/HALTexists, 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 checkfails), report the error and suggestpnpm installornpm install -g @bookedsolid/rea. - Never print the contents of
audit.jsonlbeyond whatnpx rea checksurfaces — 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
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.
- 2d ago First seen · 53 lines · 20 tokens per session scan A e2a4cb38ccca
rea is a command published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 652 once invoked, about $0.0001 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.
Other commands, from other repositories
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
test-integration
Write integration tests for component boundaries.
ijfw-execute
Jump directly to the IJFW workflow Execute phase (Deep D4 / Quick Q3). Usage: /ijfw-execute [task or phase name].
core-review
Review code changes against SpecOps project-specific patterns. Catches recurring failure modes from real PRs — tool abstraction violations, generated file drift, cross-platform gaps, variable inconsistencies, and more. Complements full-review-gate (generic quality) and pr-fix (applying bot comments).
ship-pr
Commit all changes to a new branch, push, and open a PR for review. The original branch stays clean.
_registry-protocol
This protocol is MANDATORY for ALL commands, agents, and phases.