Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Sahib-Sawhney-WH/sahibs-claude-plugin-marketplacenpx agentmods add commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/deployWrote 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/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/deploy)<a href="https://agentmods.dev/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/deploy"><img src="https://agentmods.dev/badge/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/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/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/deploy"><img src="https://agentmods.dev/badge/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/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.00014 | $0.00875 |
| Opus 5 | $0.00007 | $0.00438 |
| Sonnet 5 | $0.00003 | $0.00175 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
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 12d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DAPR Azure Deployment
Deploy your DAPR application to Azure with production-ready configuration.
Behavior
When the user runs /dapr:deploy:
-
Select Deployment Target
- Azure Container Apps (recommended for most cases)
- Azure Kubernetes Service (for advanced control)
- Ask user preference if $ARGUMENTS doesn't specify
-
Pre-Deployment Validation
- Verify Azure CLI is installed and logged in
- Check DAPR configuration is valid
- Validate Docker/container image exists
- Ensure required Azure resources exist
-
Container Apps Deployment
# Create environment if needed az containerapp env create \ --name {env-name} \ --resource-group {rg} \ --dapr-instrumentation-key {key} # Deploy DAPR components az containerapp env dapr-component set \ --name {env-name} \ --resource-group {rg} \ --dapr-component-name statestore \ --yaml ./components/statestore.yaml # Deploy application az containerapp create \ --name {app-name} \ --resource-group {rg} \ --environment {env-name} \ --image {image} \ --dapr-enabled \ --dapr-app-id {app-id} \ --dapr-app-port {port} -
AKS Deployment
# Ensure DAPR is installed on cluster dapr init -k # Apply components kubectl apply -f ./components/ # Deploy application kubectl apply -f ./k8s/deployment.yaml -
Post-Deployment
- Verify deployment succeeded
- Check DAPR sidecar is running
- Test health endpoint
- Display access URL
Arguments
$ARGUMENTS- Target and options:acaorcontainer-apps- Deploy to Azure Container Appsaksorkubernetes- Deploy to AKS--rg {name}- Resource group name--env {name}- Container Apps environment name
Examples
/dapr:deploy aca
/dapr:deploy aks --rg myapp-rg
/dapr:deploy container-apps --env production-env
Prerequisites Checked
- Azure CLI installed (
az --version) - Logged into Azure (
az account show) - Docker image built and pushed to registry
- Azure resources exist (resource group, ACR, etc.)
- DAPR components configured
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.
- 12d ago First seen · 138 lines · 14 tokens per session scan A 8c125b0fefd4
deploy is a command published in the GitHub repository Sahib-Sawhney-WH/sahibs-claude-plugin-marketplace (4 stars, last pushed 8mo ago), licensed MIT. It adds 14 tokens to every session and 875 once invoked, about $0.0001 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-31.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
Set up third-party service integrations.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.