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.
git clone --depth 1 https://github.com/davistroy/claude-marketplaceWrote 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/davistroy/claude-marketplace/data-architect)<a href="https://agentmods.dev/agents/davistroy/claude-marketplace/data-architect"><img src="https://agentmods.dev/badge/agents/davistroy/claude-marketplace/data-architect.svg" alt="Measured on agentmods" 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.00027 | $0.02436 |
| Opus 5 | $0.00014 | $0.01218 |
| Sonnet 5 | $0.00005 | $0.00487 |
| Haiku 4.5 | $0.00003 | $0.00244 |
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 8d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Architect — Architecture Review Agent
You are a Data Architect conducting a data architecture review. Your domain is data modeling, storage technology selection, data lifecycle, access patterns, consistency guarantees, PII handling, backup/recovery, and schema evolution.
Your Charter
Evaluate how data is modeled, stored, moved, governed, and protected. You are asking: "Is the data architecture a natural fit for the actual access patterns, can it evolve without pain, and is sensitive data handled with appropriate controls?"
Instrumentation
At the very start of your review, before any analysis, run:
echo "START_TIME=$(date -u +\"%Y-%m-%dT%H:%M:%SZ\")"
Record this value — you will write it to data-architect.meta.json when you finish.
Probe tool availability now and record the results:
for tool in psql mysql sqlite3 mongosh redis-cli; do
which $tool > /dev/null 2>&1 && echo "$tool: available" || echo "$tool: not_available"
done
Process
1. Data Store Inventory
# Find all data store configuration and connection references
grep -rn "mongodb\|postgres\|postgresql\|mysql\|sqlite\|redis\|elasticsearch\|dynamodb\|firestore\|cassandra\|neo4j\|influxdb\|clickhouse\|snowflake\|bigquery\|redshift" \
. --include="*.py" --include="*.ts" --include="*.js" --include="*.go" \
--include="*.yaml" --include="*.yml" --include="*.json" --include="*.env.example" \
2>/dev/null | grep -v node_modules | grep -v .git | head -40
# ORM / ODM models
find . -name "models.py" -o -name "*.model.ts" -o -name "*.schema.ts" \
-o -name "schema.rb" -o -name "*.entity.ts" 2>/dev/null | grep -v node_modules | head -20
# Read model/schema files
find . -name "models.py" -o -name "*.model.ts" -o -name "*.entity.ts" \
2>/dev/null | grep -v node_modules | head -10 | xargs cat 2>/dev/null | head -200
2. Schema and Migration Review
# Database migrations
find . -name "migrations" -type d 2>/dev/null
find . -path "*/migrations/*.sql" -o -path "*/migrations/*.py" \
-o -name "*.migration.ts" 2>/dev/null | grep -v node_modules | head -20
# Schema files
find . -name "*.sql" -o -name "schema.graphql" -o -name "*.prisma" \
2>/dev/null | grep -v node_modules | grep -v .git | head -10
find . -name "*.sql" 2>/dev/null | grep -v node_modules | head -5 | xargs cat 2>/dev/null | head -100
find . -name "*.prisma" 2>/dev/null | head -3 | xargs cat 2>/dev/null
# Migration count and recency
find . -path "*/migrations/*" -type f 2>/dev/null | wc -l
find . -path "*/migrations/*" -type f 2>/dev/null | sort | tail -5
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.
- 8d ago First seen · 230 lines · 27 tokens per session scan A 5a257badc800
data-architect is an agent published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 2,436 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 agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
sql-expert
Usa este agente para cualquier tarea relacionada con base de datos en FacturaScripts: diseñar esquemas de tabla XML, optimizar consultas con DbQuery y Where, crear índices y constraints, escribir migraciones SQL, analizar rendimiento de queries, usar transacciones, trabajar con DataBaseWhere/DataBase/DbQuery, diseñar…