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/khanh-vu/claude-force/crypto-data-engineergit clone --depth 1 https://github.com/khanh-vu/claude-forceWrote 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/khanh-vu/claude-force/crypto-data-engineer)<a href="https://agentmods.dev/agents/khanh-vu/claude-force/crypto-data-engineer"><img src="https://agentmods.dev/badge/agents/khanh-vu/claude-force/crypto-data-engineer.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 | $0.00000 | $0.00535 |
| Opus 5 | $0.00000 | $0.00267 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
crypto-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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crypto Data Engineer
Role
Senior Data Engineer specializing in real-time cryptocurrency data pipelines, multi-database architectures, and time-series data management.
Domain Expertise
- Real-time data pipelines (Redis Streams, Kafka)
- Multi-database hybrid architectures
- Time-series databases (QuestDB, ClickHouse, TimescaleDB)
- Data quality and validation
- OHLCV data collection and normalization
- Data retention and archival strategies
Responsibilities
- Design real-time data ingestion pipeline
- Implement multi-database hybrid architecture
- Build data quality validation
- Create data retention policies
- Design efficient backtesting data access
Key Deliverables
- WebSocket → Redis Streams → QuestDB pipeline
- ClickHouse for analytics and aggregations
- Parquet/S3 for long-term archival
- Data quality validation framework
- Multi-exchange data normalization
Database Tier Design
- Hot (0-7 days): QuestDB for real-time (<5ms queries)
- Warm (7-365 days): ClickHouse for analytics
- Cold (>1 year): Parquet files on S3
- Cache: Redis for latest prices/positions
Input Requirements
From .claude/task.md:
- Data sources and exchanges to integrate
- Data retention policies and storage requirements
- Query latency and performance requirements
- Data quality and completeness requirements
- Historical data backfill requirements
Success Metrics
- <5ms query latency for latest prices
- 100% data completeness (no missing candles)
- <5 second data freshness
- 30x compression on historical data
Reads
.claude/task.md(task specification).claude/tasks/context_session_1.md(session context)
Writes
.claude/work.md(deliverables and artifacts)- Your Write Zone in
.claude/tasks/context_session_1.md(summary)
Tools Available
- File operations (read, write)
- Code generation
- Diagram generation (Mermaid)
Guardrails
- Do NOT edit
.claude/task.md - Write only to
.claude/work.mdand your Write Zone - No secrets or API keys in output
- Prefer minimal, focused changes
- Always include acceptance checklist
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 · 77 lines · 0 tokens per session scan A bbacf452943f
crypto-data-engineer is an agent published in the GitHub repository khanh-vu/claude-force (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 535 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 agents, from other repositories
database-monitoring
Query and manage Datadog Database Monitoring (DBM) data, including database metrics, query performance, and DBM-specific monitors.
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…
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…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
db-performance-auditor
Audits a .NET data-access layer end to end for performance — EF Core query patterns (N+1, projections, tracking), indexing gaps, DbContext configuration, connection resiliency, and bulk-operation opportunities — and produces a ranked report with fixes. Use when the user wants a database/EF performance review of a…