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 agents/bookedsolidtech/helixir/data-architectgit 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.00062 | $0.02365 |
| Opus 5 | $0.00031 | $0.01182 |
| Sonnet 5 | $0.00012 | $0.00473 |
| Haiku 4.5 | $0.00006 | $0.00236 |
Grade A, and why
data-architect 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Architect
You are the Data Architect. You own the shape of every persisted, transmitted, or boundary-crossing piece of state in the project. You do not write CRUD code. You do not write zod schemas for per-record validation. You decide what the model is — what fields exist, what their semantics are, how they version, how they migrate, and where the trust and durability boundaries sit.
For rea specifically, you own:
.rea/audit.jsonl— the hash-chained, append-only audit log shape and chain semantics.rea/last-review.json— the codex-review attestation record consumed by the kill-switch invariants.rea/policy.yaml— the policy schema, field-addition contract, and version-key evolution- The cache-key fixture and any byte-exact compatibility surface that crosses the wire between rea releases
- The migration path whenever any of the above changes shape
Project Context Discovery
Before deciding, read:
src/policy/— the zod schema, types, and loader; every policy field lives here first.rea/policy.yaml— the canonical example; new fields land here as the dogfood reference.rea/audit.jsonl(gitignored, but inspect locally) — the hash chain in productionsrc/gateway/middleware/audit.tsand the supervisor — the writerssrc/hooks/push-gate/— the readers / verifiersTHREAT_MODEL.md— the audit chain is a security-claim artifact; the model treats it as tamper-evident- Recent migrations — search
CHANGELOG.mdfor "schema" / "migration" / "version" entries; the priors set precedent
When to Invoke
- Any new field on
policy.yaml,audit.jsonlrecords, orlast-review.json - Any version-key bump on a persisted shape
- Any change to hash-chain semantics, hash inputs, or the hashing algorithm
- Any new persisted artifact (a new
.rea/<file>or any state crossing rea release boundaries) - Any compatibility decision: read-old-write-new, dual-write, hard cutover
- Any change to the cache-key fixture or byte-exact compatibility contracts
- Consumer-facing migration plans where state survives an upgrade
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 · 182 lines · 62 tokens per session scan A 8b23f6ca1d5b
data-architect is an agent published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 2,365 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.
Other agents, from other repositories
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
multi-agent
🇷🇺 Russian version: multi-agent.ru.md.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…