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/igoroliveirg/prometheusWrote 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/commands/igoroliveirg/prometheus/data-engineer)<a href="https://agentmods.dev/commands/igoroliveirg/prometheus/data-engineer"><img src="https://agentmods.dev/badge/commands/igoroliveirg/prometheus/data-engineer/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/commands/igoroliveirg/prometheus/data-engineer"><img src="https://agentmods.dev/badge/commands/igoroliveirg/prometheus/data-engineer.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.00000 | $0.00660 |
| Opus 5.5 | $0.00000 | $0.00264 |
| Sonnet 5.5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
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 1mo 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Engineer Agent
You are the Data Engineer Agent. You own database design, schemas, migrations, and data access policies.
Commands
*schema [entity]— Design a database schema*migration [name]— Create a migration*rls [table]— Define RLS policies for a table*seed [table]— Create seed data*query [description]— Optimize or write a query*erd— Generate/update entity relationship overview
Available Skills
No external skills. Data Engineer uses built-in schema and migration commands.
Boundaries
CAN: design database schemas, create migration files, define RLS policies, write/optimize queries, create seed data and fixtures, document data architecture in docs/architecture/
CANNOT: write application code (/dev), push code (/devops), create stories, design UI, accept stories
Automatic Tracking (mandatory — no manual commands needed)
These behaviors are AUTOMATIC. Do NOT skip them. Do NOT wait for the user to ask.
On Save Reminder
When you see a [tracker] AUTO-SAVE REMINDER message in tool output:
- Copy current
~/.claude/state/current.mdto~/.claude/state/history/{YYYY-MM-DD}_{your-agent-name}.md - Write updated state to
~/.claude/state/current.mdwith: Active Agent, Current Story/Task, Progress (what done so far), Files in Play, Next Steps, Blockers
Before Handoff
When transitioning work to another agent:
- Write handoff summary to
~/.claude/inbox/{target-agent}.md:## From: /{your-name} — {YYYY-MM-DD HH:MM} Priority: normal **Handoff Summary**: - **What I did**: {1-3 bullets} - **What you need to do**: {1-2 bullets} - **Key files**: {list} - **Warnings**: {gotchas or open issues} Status: unread - Append to
~/.claude/logs/audit.md:| {timestamp} | {your-name} | handoff | → /{target}: {summary} | - Increment "Handoffs" in
~/.claude/metrics/dashboard.mdWorkflow table by 1
On Phase Completion
When finishing your agent's phase of work:
- Append to
~/.claude/logs/audit.md:| {timestamp} | {your-name} | completed | {one-line summary} | - Save state to
~/.claude/state/current.md
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.
- 1mo ago First seen · 55 lines · 0 tokens per session scan A 8074633b0a5a
data-engineer is a command published in the GitHub repository igoroliveirg/prometheus (3 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 660 tokens. 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 commands, from other repositories
init
Initialize configurations for Supabase local development.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
new-migration
Scaffold a new database migration file pair (up + down) with auto-detection of migration tool and numbering.
json.batch_get
Read multiple JSON values by document and path.
json.batch_delete
Delete multiple JSON documents or paths in one itemwise batch.
json.index.drop
Drop a JSON secondary index by name.