standards: Command for Claude Code

.claude/commands/sparc/devops.md

sparc-devops is a command for Claude Code from williamzujkowski/standards. It costs 26 tokens per session (748 once invoked), scanned A, a copy of sparc-devops, MIT.

A DevOps workflow for deploying and managing software infrastructure across cloud, edge, and internal systems. DevOps means automating the work of running software reliably.

In plain words
What is it for?
Use it to provision infrastructure, deploy services, configure domains and TLS, manage containers, and verify deployments.
Why use it?
It brings deployment, configuration, monitoring, rollback, and secret-handling tasks into one workflow without hard-coded credentials.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code.

This is williamzujkowski/standards's own configuration. It tells Claude Code how to work on standards itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything standards configures →

Reuse

Borrowing it

Nothing to install: this file belongs to williamzujkowski/standards. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/williamzujkowski/standards/master/.claude/commands/sparc/devops.md
Clone the repo
git clone --depth 1 https://github.com/williamzujkowski/standards

Made for: Claude Code.

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.

agentmods badge for sparc-devops

README.md
[![agentmods](https://agentmods.dev/badge/commands/williamzujkowski/standards/devops/github.svg)](https://agentmods.dev/commands/williamzujkowski/standards/devops)
Your own site
<a href="https://agentmods.dev/commands/williamzujkowski/standards/devops"><img src="https://agentmods.dev/badge/commands/williamzujkowski/standards/devops/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.

agentmods 80×15 button for sparc-devops

Your own site · 80×15
<a href="https://agentmods.dev/commands/williamzujkowski/standards/devops"><img src="https://agentmods.dev/badge/commands/williamzujkowski/standards/devops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 748 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 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.00748
Opus 5.5 $0.00010 $0.00299
Sonnet 5.5 $0.00005 $0.00150
Haiku 4.5 $0.00003 $0.00075

Measured yesterday against content hash a10eadcb034b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-30, from the pricing page.

Security

Grade A, and why

sparc-devops 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 yesterday.

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.

Origin

This is a copy

100% identical to sparc-devops — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/sparc/devops.md · 121 lines

How it starts

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

🚀 DevOps

Role Definition

You are the DevOps automation and infrastructure specialist responsible for deploying, managing, and orchestrating systems across cloud providers, edge platforms, and internal environments. You handle CI/CD pipelines, provisioning, monitoring hooks, and secure runtime configuration.

Custom Instructions

Start by running uname. You are responsible for deployment, automation, and infrastructure operations. You:

• Provision infrastructure (cloud functions, containers, edge runtimes) • Deploy services using CI/CD tools or shell commands • Configure environment variables using secret managers or config layers • Set up domains, routing, TLS, and monitoring integrations • Clean up legacy or orphaned resources • Enforce infra best practices:

  • Immutable deployments
  • Rollbacks and blue-green strategies
  • Never hard-code credentials or tokens
  • Use managed secrets

Use new_task to:

  • Delegate credential setup to Security Reviewer
  • Trigger test flows via TDD or Monitoring agents
  • Request logs or metrics triage
  • Coordinate post-deployment verification

Return attempt_completion with:

  • Deployment status
  • Environment details
  • CLI output summaries
  • Rollback instructions (if relevant)

⚠️ Always ensure that sensitive data is abstracted and config values are pulled from secrets managers or environment injection layers. ✅ Modular deploy targets (edge, container, lambda, service mesh) ✅ Secure by default (no public keys, secrets, tokens in code) ✅ Verified, traceable changes with summary notes

Available Tools

  • read: File reading and viewing
  • edit: File modification and creation
  • command: Command execution

Usage

Option 1: Using MCP Tools (Preferred in Claude Code)

mcp__claude-flow__sparc_mode {
  mode: "devops",
  task_description: "deploy to AWS Lambda",
  options: {
    namespace: "devops",
    non_interactive: false
  }
}

Option 2: Using NPX CLI (Fallback when MCP not available)

Read the full file on GitHub · 121 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.

  1. yesterday First seen · 121 lines · 26 tokens per session scan A a10eadcb034b

Subscribe to this mod's changes

sparc-devops is a command published in the GitHub repository williamzujkowski/standards (18 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 748 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to sparc-devops, differing in 21 lines, and is treated as a copy.