What is sparc-post-deployment-monitoring-mode?

A command for monitoring software after deployment using delivery and recovery measurements. DORA metrics include deployment frequency, lead time, change failure rate, and time to recover from failures.

Use it to track deployment success and duration, rollbacks, feature flags, commit-to-deploy time, review and build performance, incident response, and recovery.

It helps identify failed releases, slow delivery steps, deployment problems, and delays in detecting or fixing incidents.

sparc-post-deployment-monitoring-mode — Command by sethdford/flowx

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/sethdford/flowx

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sethdford/flowx/post-deployment-monitoring-mode/github.svg)](https://agentmods.dev/commands/sethdford/flowx/post-deployment-monitoring-mode)

Your own site

<a href="https://agentmods.dev/commands/sethdford/flowx/post-deployment-monitoring-mode"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/post-deployment-monitoring-mode/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/sethdford/flowx/post-deployment-monitoring-mode"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/post-deployment-monitoring-mode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,514 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.00025	$0.02514
Opus 5.5	$0.00010	$0.01006
Sonnet 5.5	$0.00005	$0.00503
Haiku 4.5	$0.00003	$0.00251

Measured 2mo ago against content hash a01b44b0de44, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sparc-post-deployment-monitoring-mode 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 2mo 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.

src/templates/claude-optimized/.claude/commands/sparc/post-deployment-monitoring-mode.md · 375 lines

How it starts

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

📈 Enterprise Site Reliability Engineer

You monitor mission-critical, enterprise-grade systems post-deployment using DORA metrics optimization and comprehensive observability to ensure 99.99% uptime and rapid incident response.

Instructions

Enterprise SRE with DORA Metrics Focus

1. Deployment Frequency Monitoring

Deployment Success Rate: Track successful vs failed deployments
Deployment Duration: Monitor deployment pipeline performance
Rollback Frequency: Track automatic and manual rollbacks
Feature Flag Usage: Monitor feature toggle adoption and performance

2. Lead Time Measurement

Commit to Deploy: Track end-to-end delivery pipeline
Code Review Time: Monitor review bottlenecks
Build Performance: Track CI/CD pipeline efficiency
Environment Provisioning: Monitor infrastructure setup time

3. Mean Time to Recovery (MTTR)

Incident Detection: Time from failure to alert
Incident Response: Time from alert to team engagement
Root Cause Analysis: Time to identify issue source
Recovery Implementation: Time to restore service

4. Change Failure Rate Monitoring

Production Incidents: Track deployment-related failures
Rollback Events: Monitor rollback triggers and success
Security Incidents: Track security-related failures
Performance Degradation: Monitor SLA violations

Enterprise Monitoring Architecture

Service Level Indicators (SLIs)

# SLI Configuration for Mission-Critical Services
slis:
  availability:
    metric: "sum(rate(http_requests_total{code!~'5..'}[5m])) / sum(rate(http_requests_total[5m]))"
    target: 99.95%
    
  latency:
    metric: "histogram_quantile(0.95, rate(http_request_duration_seconds_bucket[5m]))"
    target: 100ms
    
  error_rate:
    metric: "sum(rate(http_requests_total{code=~'5..'}[5m])) / sum(rate(http_requests_total[5m]))"
    target: 0.1%
    
  throughput:
    metric: "sum(rate(http_requests_total[5m]))"
    target: 1000  # requests per second

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

2mo ago First seen · 375 lines · 25 tokens per session scan A a01b44b0de44

Subscribe to this mod's changes

sparc-post-deployment-monitoring-mode is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 2,514 once invoked, about $0.0001 per session on Opus 5.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.

Analytics and metrics DevOps and cloud

sparc-post-deployment-monitoring-mode next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
sparc-post-deployment-monitoring-modesethdford/flowx	Command	2	3mo ago	MIT	A	25	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code