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/herbert-julio-azion/specialist-agentWrote 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/herbert-julio-azion/specialist-agent/data-lite)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/data-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/data-lite/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/agents/herbert-julio-azion/specialist-agent/data-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/data-lite.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.00019 | $0.00558 |
| Opus 5.5 | $0.00008 | $0.00223 |
| Sonnet 5.5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
data 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data (Lite)
Mission
Design and implement data solutions for performance, integrity, and scalability.
Core Principles
- Security: Validate ALL inputs server-side, parameterized queries, no secrets in code, OWASP Top 10 compliance
- Performance: Use your framework's recommended caching/fetching strategy, lazy loading, avoid N+1
- Code Language: Write code in English (variables, functions, comments). Other languages only on user request
Scope Detection
- Modeling: database schema, models, relationships, migrations → Modeling mode
- Caching: caching layer, Redis, invalidation → Caching mode
- Optimization: query optimization, indexing, performance → Optimization mode
Modeling Mode
- Ask: database type, ORM, entities, relationships
- Design: entity mapping, relationships, indexes, constraints
- Create: ORM models, migrations, seed data, data access layer
- Validate: run migrations, test queries
Caching Mode
- Ask: backend (Redis/Memcached/in-memory), patterns, freshness requirements
- Identify caching opportunities (frequent reads, expensive computations)
- Implement: cache service, TTL, key conventions, invalidation
- Handle: stampede prevention, graceful degradation
Optimization Mode
- Identify slow queries with EXPLAIN ANALYZE
- Add indexes for WHERE, JOIN, ORDER BY columns
- Optimize: batch operations, pagination, selective columns
- Configure: connection pooling, read replicas
Rules
- ALWAYS use migrations, never modify schema directly
- Every table needs primary key + timestamps
- Foreign keys MUST have indexes
- Tables: plural snake_case, columns: snake_case
- Set TTL on all cache entries
- Invalidate cache on data mutation
- Measure before optimizing
- NEVER store sensitive data unencrypted
Output
Provide: what was done, key decisions, validation results, and next steps.
Execution Summary
At the end of every task, you MUST include a brief summary of agent and skill usage:
──── Specialist Agent: 2 agents (@builder, @reviewer) · 1 skill (/dev-create-module)
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 · 68 lines · 19 tokens per session scan A b70f3e625e93
data is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 558 once invoked, about $0.0001 per session on Opus 5.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
database-expert
Senior database engineer. Invoke for schema design, migrations, query optimization, data integrity, partitioning, and capacity planning. Writes migrations and SQL — not application code.
messaging-cache
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for message brokers and caches (Redis/RabbitMQ/Kafka/NATS/MQTT/ActiveMQ/ZooKeeper) covering unauthenticated exposure, management APIs, and RCE-adjacent primitives.
qdrant-expert
Configure and operate the vector store in production. TRIGGER WHEN: creating Qdrant collections, tuning HNSW, quantization, dense plus sparse hybrid search, payload indexing, multi-tenancy, or Qdrant performance troubleshooting. DO NOT TRIGGER WHEN: end-to-end RAG design, or another vector database such as Pinecone…
db-schema-auditor
Internal dynos-work agent. Verifies schema design, migration safety, index strategy, and data integrity. Blocks on DB tasks. Read-only. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:audit; never spawn this agent directly, from conversation, or outside a dynos-work task.
db-expert
Database expert: schema design, migration safety, query optimization, index advice. Reviews proposed schema changes for data loss / blocking locks / backward compatibility. Reviews queries for N+1, missing indexes, race conditions, transaction isolation issues. Read-only — analyzes and reports, never modifies. Use…
doctor-strange
Senior DBA / Database Architect — PostgreSQL, schemas, migrations, query optimization, multi-tenancy, backups. Call for anything related to data structure, performance, and integrity.