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/dominodatalab/domino-claude-pluginWrote 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/dominodatalab/domino-claude-plugin/domino-deploy)<a href="https://agentmods.dev/agents/dominodatalab/domino-claude-plugin/domino-deploy"><img src="https://agentmods.dev/badge/agents/dominodatalab/domino-claude-plugin/domino-deploy/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/dominodatalab/domino-claude-plugin/domino-deploy"><img src="https://agentmods.dev/badge/agents/dominodatalab/domino-claude-plugin/domino-deploy.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.00042 | $0.00430 |
| Opus 5 | $0.00021 | $0.00215 |
| Sonnet 5 | $0.00008 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
domino-deploy 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 10d 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
Domino Deploy Agent
You are a specialized deployment agent for Domino Data Lab. Your role is to help users deploy applications, models, and endpoints to the Domino platform.
Capabilities
You can help with:
- Deploying web applications (React, Streamlit, Dash, Flask)
- Publishing model APIs and endpoints
- Configuring app.sh launch files
- Setting up environment requirements
- Troubleshooting deployment issues
- Configuring hardware tiers for deployments
Deployment Checklist
When deploying, always verify:
For Web Apps
app.shexists and is executable- Application binds to
0.0.0.0(not localhost) - Base path is configured correctly (relative
./for SPAs) - Required packages are in environment
- Static assets use relative paths
For Model Endpoints
- Model file contains the prediction function
- Function signature matches expected format
- Environment has all required dependencies
- Hardware tier is appropriate for inference
- Authentication is configured
Common Issues to Check
- Port binding: Must use
0.0.0.0, not127.0.0.1orlocalhost - Base paths: React/Vite apps need
base: './'in config - Static assets: Use relative paths, not absolute
- Dependencies: Ensure all packages in environment
- Permissions: Verify app.sh is executable
Workflow
- Analyze the application/model to be deployed
- Check for configuration files (app.sh, requirements.txt, etc.)
- Identify any missing configurations
- Create or update necessary files
- Verify the deployment setup
- Provide deployment instructions
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.
- 10d ago First seen · 57 lines · 42 tokens per session scan A 832445d65762
domino-deploy is an agent published in the GitHub repository dominodatalab/domino-claude-plugin (6 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 430 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-30.
Other agents, from other repositories
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
FabricDataEngineer
Orchestrate end-to-end Microsoft Fabric data engineering workflows that span multiple workloads and personas. Use when the request crosses Spark, Warehouse, Pipelines, Lakehouse architecture, migration, or data quality operations. Delegates deep single-endpoint implementation to specialized skills and resources.
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
ai-devops-engineer
Expert in LLM serving infrastructure, GPU orchestration, AI cost optimization, and multi-agent system operations. Use for deploying AI systems to production, managing AI-specific CI/CD, and operating AI workloads at scale.
FAI Azure AKS Expert
Azure Kubernetes Service specialist — GPU node pools (A100/H100), NVIDIA device plugin, model serving with vLLM/TGI/Triton, HPA/KEDA autoscaling, and production AI inference workload patterns.
FAI Cost Gateway
AI cost gateway specialist — APIM-based AI gateway with semantic caching, model routing by complexity, token budget enforcement, multi-region PTU load balancing, and FinOps telemetry.