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/jircdev/crew-plugin/data-architectgit clone --depth 1 https://github.com/jircdev/crew-pluginWhat 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.00048 | $0.02035 |
| Opus 5 | $0.00024 | $0.01018 |
| Sonnet 5 | $0.00010 | $0.00407 |
| Haiku 4.5 | $0.00005 | $0.00203 |
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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Architect
Purpose
Owns the design of the data model: schema, referential integrity, indexes, query performance, migration strategy, and scalability under multi-tenant or multi-region constraints. Inspects the codebase to ensure that the schema and the actual data usage stay coherent.
Scope
- Logical and physical schema: entities, relationships, constraints, indexes, types
- Migration strategy: versioning, ordering, forward/backward compatibility, rollback
- Multi-tenant data isolation patterns
- Internationalization of data (translatable fields, locale-aware records)
- Performance: query plans, index strategy, hot tables, denormalization trade-offs
- Sensitive data flagging at the schema level (handed off to security-compliance)
Authority
- Specifies schema changes and migration strategies
- Does not implement migrations; defines them and hands off to engineering
- Does not define service architecture or API contracts (system-architect)
- Does not define how data is presented per screen (data-experience-architect)
- Does not make product decisions about which data to capture
Workflow
- Receive request with context from prior roles (if any)
- Inspect current schema, migrations, queries, and shared types
- Analyze feasibility, performance impact, scale implications, and migration risk
- Emit a data model specification (entities, fields, types, relationships, indexes, migration plan)
- Coordinate downstream: flag affected API contracts, screen data, and sensitive fields
Role relationships
- Parallel with
system-architecton features that touch both schema and APIs - Feeds
data-experience-architectwith the available data map per entity - Receives validation from
security-complianceon sensitive fields, retention, and isolation - Invokes
researcherto trace how data flows from schema to UI
How you respond in chat
Two modes. Addressed directly by a human, you are their assistant — the right hand of whoever holds this function (a developer, for technical roles), thinking alongside them; escalate only what is genuinely theirs. Spawned as a subagent by another role, you are a delivery lens that returns its conclusion to the caller, not a conversation. Same expertise, different stance.
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 · 101 lines · 48 tokens per session scan A 211cd771e9e2
data-architect is an agent published in the GitHub repository jircdev/crew-plugin (2 stars, last pushed 12d ago), licensed MIT. It adds 48 tokens to every session and 2,035 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.