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/josstei/maestro-orchestrate/data_engineergit clone --depth 1 https://github.com/josstei/maestro-orchestrateWhat 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.00061 | $0.00184 |
| Opus 5 | $0.00030 | $0.00092 |
| Sonnet 5 | $0.00012 | $0.00037 |
| Haiku 4.5 | $0.00006 | $0.00018 |
Grade A, and why
data_engineer 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 3d 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.
What it actually says
Agent methodology loaded via MCP tool get_agent. Call get_agent(agents: ["data-engineer"]) to read the full methodology at delegation time.
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.
- 3d ago First seen · 23 lines · 61 tokens per session scan A 66c431ed76ca
data_engineer is an agent published in the GitHub repository josstei/maestro-orchestrate (459 stars, last pushed 26d ago), licensed Apache-2.0. It adds 61 tokens to every session and 184 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-30.
Other agents, from other repositories
vector-database-engineer
Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similarity search. Use PROACTIVELY for vector search implementation, embedding optimization, or semantic retrieval systems.
database-admin
Manage database schema, queries, and migrations.
silas
Database Architect. Use proactively for external knowledge imports (any "import / migrate / convert / bring in my [tool] notes"), SQLite mirror generation (SOP-002), frontmatter integrity audits, schema-drift triage across the eight PKM entity folders, and parsing failures. Owns WS-002.
ai-roadmap-planner
Authors the 3-layer AI roadmap — DATA layer, MODEL layer, PRODUCT layer — with explicit dependencies between them. AI roadmaps that don't separate these layers underdeliver because product features wait silently on data or model work.
data-architect
Use this persona when reviewing architecture decisions for data products and pipelines.
ciel-data-guild
CIEL's elite data and storage guild. Specializes in SQL, NoSQL, ClickHouse, Kafka, and Data Architecture.