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/Sahib-Sawhney-WH/sahibs-claude-plugin-marketplaceWrote 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/cicd)<a href="https://agentmods.dev/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/cicd"><img src="https://agentmods.dev/badge/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/cicd/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/cicd"><img src="https://agentmods.dev/badge/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/cicd.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.00017 | $0.00634 |
| Opus 5 | $0.00009 | $0.00317 |
| Sonnet 5 | $0.00003 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
cicd 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DAPR CI/CD Generator
Generate production-ready CI/CD pipelines for your DAPR application.
Behavior
When the user runs /dapr:cicd:
-
Detect Project Structure
- Identify main application file
- Find test directories
- Locate component YAML files
- Detect Dockerfile
-
Generate CI Pipeline
- Linting and type checking
- Unit tests with coverage
- DAPR configuration validation
- Security scanning
- Container build
-
Generate CD Pipeline
- Staging deployment
- Health checks
- Production deployment (blue-green)
- Rollback on failure
Arguments
| Argument | Description |
|---|---|
github |
Generate GitHub Actions workflows (default) |
azure-devops |
Generate Azure DevOps pipelines |
--target aca |
Target Azure Container Apps |
--target aks |
Target Azure Kubernetes Service |
Examples
GitHub Actions for Container Apps
/dapr:cicd github --target aca
Azure DevOps for AKS
/dapr:cicd azure-devops --target aks
Generated Files
GitHub Actions
.github/
└── workflows/
├── ci.yml # Build, test, validate
├── cd-aca.yml # Deploy to Container Apps
└── cd-aks.yml # Deploy to AKS
Azure DevOps
azure-pipelines/
├── azure-pipelines.yml # Main pipeline
├── templates/
│ ├── build.yml # Build template
│ ├── test.yml # Test template
│ └── deploy.yml # Deploy template
└── variables/
├── staging.yml # Staging variables
└── production.yml # Production variables
Pipeline Features
CI Pipeline
- Ruff linting and MyPy type checking
- Unit tests with pytest and coverage
- DAPR configuration validation
- Security scanning with Trivy
- Container image build and push
CD Pipeline
- Environment-based deployments
- Blue-green deployment strategy
- Health check verification
- Automatic rollback on failure
- DAPR component updates
Required Secrets
GitHub Actions
| Secret | Description |
|---|---|
AZURE_CREDENTIALS |
Azure service principal JSON |
AZURE_RESOURCE_GROUP |
Resource group name |
AZURE_CONTAINER_REGISTRY |
ACR name |
CONTAINER_APP_NAME |
Container Apps name |
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 · 110 lines · 17 tokens per session scan A 753aeeed1903
cicd 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 17 tokens to every session and 634 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
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
ship
Deploy feature through automated staging validation to production with rollback testing.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.