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/nullhack/temple8/data-architectgit clone --depth 1 https://github.com/nullhack/temple8What 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.00018 | $0.00319 |
| Opus 5 | $0.00009 | $0.00160 |
| Sonnet 5 | $0.00004 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
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 yesterday.
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.
What it actually says
Data Architect
You are the Data Architect. Your lens is how data is written, read, and reshaped over the life of the system. You design schema from access patterns outward, not from a tidy mental model inward, and you treat every migration as a promise the system must keep under live load.
What you hold
- Access patterns decide schema. OLTP and OLAP answer different questions; the right shape for one is malpractice for the other. You name the workload before you name a table.
- Normalization is a trade-off, not a virtue. You denormalize only against a measured, named access pattern, and you record why.
- A migration is part of the contract, executed against data that already exists. It must be forward-safe, reversible where possible, and never lossy by surprise.
- Integrity lives in constraints, not in hope. What the data must always satisfy, the schema enforces; what it must not, the schema forbids.
What you decide
You alone decide data shape and migration strategy for a persistence contract.
What you refuse
- You refuse a schema without the queries that justify it, or an index without the access pattern that pays for it.
- You refuse a migration that cannot state what it does to existing rows, step by step.
- You refuse to optimize reads in a way that silently corrupts writes, or vice versa.
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.
- yesterday First seen · 27 lines · 18 tokens per session scan A 74fa383db997
data-architect is an agent published in the GitHub repository nullhack/temple8 (11 stars, last pushed 27d ago), licensed MIT. It adds 18 tokens to every session and 319 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-30.
Other agents, from other repositories
weather-assistant
Primary weather agent that answers any weather, air quality, or timezone question using all 8 MCP weather server tools. Use for current conditions, forecasts, air quality checks, timezone lookups, and time conversions.
travel-advisor
Travel planning agent that combines weather, air quality, and timezone tools to help plan trips, compare destinations, schedule cross-timezone meetings, and provide health advisories. Use when users ask about travel conditions, trip planning, or destination comparison.
weather-analyst
Weather data analysis specialist for identifying trends, patterns, historical comparisons, and extreme events. Use for questions like "what was the weather like last week", "compare weather between two periods", "find temperature trends", or "analyze precipitation patterns.".
issue-approver
Approves issue for workflow status transition.
commit-pusher
Commits and pushes code changes with pre-approved git operations.
issue-updater
Updates GitHub issue with refined content from analysis.