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.
curl -O https://raw.githubusercontent.com/bookedsolidtech/helixir/main/.claude/agents/data-architect.mdgit clone --depth 1 https://github.com/bookedsolidtech/helixirWrote 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.
[](https://agentmods.dev/agents/bookedsolidtech/helixir/data-architect)<a href="https://agentmods.dev/agents/bookedsolidtech/helixir/data-architect"><img src="https://agentmods.dev/badge/agents/bookedsolidtech/helixir/data-architect/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.
<a href="https://agentmods.dev/agents/bookedsolidtech/helixir/data-architect"><img src="https://agentmods.dev/badge/agents/bookedsolidtech/helixir/data-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00062 | $0.02365 |
| Opus 5.5 | $0.00025 | $0.00946 |
| Sonnet 5.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 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.
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.
- 2mo 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 4mo ago), licensed MIT. It adds 62 tokens to every session and 2,365 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-08-31.
Other agents, from other repositories
data-engineer
ETL pipelines, data warehousing, stream processing, and data infrastructure specialist. Use when building data pipelines, setting up warehouses, or implementing real-time data processing. Trigger phrases: ETL, pipeline, data warehouse, BigQuery, Snowflake, Redshift, Kafka, Airflow, dbt, streaming, data lake, data…
database-expert
Expert database architect and engineer for PostgreSQL, MongoDB, Redis, and all major databases. Use when designing schemas, optimizing queries, planning migrations, implementing caching, or troubleshooting database performance.
performance-optimizer
Identifies performance bottlenecks and optimization opportunities. Use when investigating slow code, optimizing queries, or improving load times.
data-engineer
Data engineering specialist — dbt/Snowflake validation, Jupyter notebooks, data artifact stewardship. Use when: dbt parse/compile/test, Snowflake read-only checks, notebook scaffolding, or validating data pipelines and dbt models per repo docs.
db-analyst
Analyzes database schemas, queries, migrations, and performance. Use for schema reviews, query optimization, and migration planning across any ORM.
database-migrator
A database migration specialist who plans and executes schema changes, data transformations, and zero-downtime migrations. Treats every migration as a production deployment — with rollback plans, data validation, and phased execution.