A command for checking the health of a Dapr installation, its running applications, local components, and eligible Azure deployments. Dapr is a runtime that supports communication and other shared functions in distributed applications.

Use it to inspect Dapr and application status, validate component YAML files and connectivity, and review Azure Container Apps, identities, configurations, and recent logs when Azure CLI is available.

It brings version, runtime, application, component, and deployment problems into one status report instead of requiring separate checks.

status — Command for Claude Code by Sahib-Sawhney-WH

Install

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.

Clone the repo

git clone --depth 1 https://github.com/Sahib-Sawhney-WH/sahibs-claude-plugin-marketplace

Made for: Claude Code.

Or install dapr, the plugin that ships this one along with the rest of its 9 skills, 14 commands, 8 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/status/github.svg)](https://agentmods.dev/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/status)

Your own site

<a href="https://agentmods.dev/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/status"><img src="https://agentmods.dev/badge/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/status/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/status"><img src="https://agentmods.dev/badge/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 727 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00013	$0.00727
Opus 5	$0.00006	$0.00364
Sonnet 5	$0.00003	$0.00145
Haiku 4.5	$0.00001	$0.00073

Measured 12d ago against content hash 87a799f6dce9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

status 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.

plugins/dapr/commands/status.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DAPR Status Check

Check the health and status of your DAPR installation, running applications, and Azure deployments.

Behavior

When the user runs /dapr:status:

Check Local DAPR Installation
```
dapr --version
dapr status
```
Report:
- DAPR CLI version
- DAPR runtime version
- Control plane status (placement, sentry, operator)
- Dashboard availability
Check Running Applications
```
dapr list
```
Display table of:
- App ID
- HTTP Port
- gRPC Port
- App Port
- Age
- Status
Validate Local Components
- Scan components/ directory
- Validate each YAML file
- Check component connectivity (Redis, etc.)
- Report any configuration issues
Check Azure Status (if Azure CLI available)
- Container Apps environment status
- Deployed DAPR applications
- Component configurations
- Managed identity status
- Recent deployment logs

Health Summary

DAPR Status Report
==================

Local Environment:
├── DAPR CLI:        v1.12.0 ✓
├── Runtime:         v1.12.0 ✓
├── Dashboard:       Running ✓
└── Components:      3 loaded ✓

Running Apps:
├── order-service:   Running (port 8000)
└── inventory-svc:   Running (port 8001)

Azure (Container Apps):
├── Environment:     my-env ✓
├── Apps:            2 deployed
└── Last Deploy:     2 hours ago

Arguments

$ARGUMENTS - Scope: local, azure, all (default: all)

Examples

/dapr:status
/dapr:status local
/dapr:status azure

Detailed Checks

Component Health

For each component, verify:

YAML syntax valid
Required metadata present
Connection successful (for state stores, pubsub)
Secrets accessible (if referenced)

Azure Integration

If Azure resources detected:

Check az CLI authentication
Query Container Apps status
List DAPR components in Azure
Show resource group details

Troubleshooting Output

When issues found, provide actionable fixes:

Read the full file on GitHub · 125 lines

Changes

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 · 125 lines · 13 tokens per session scan A 87a799f6dce9

Subscribe to this mod's changes

status 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 13 tokens to every session and 727 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.

Cloud DevOps and cloud

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…

wshobson/agents · 0 tokens

deploy

Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.

butterbase-ai/butterbase-skills · 20 tokens

integrate

Set up third-party service integrations.

nxtg-ai/forge-plugin · 6 tokens

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.

vercel/vercel-plugin · 35 tokens

scan

Scan AWS account for cost optimization.

prajapatimehul/claude-aws-cost-saver · 6 tokens

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.

glassity/agent-skills · 57 tokens