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

A post-launch monitoring workflow that watches performance data, logs, uptime checks, and user feedback for regressions or unexpected behaviour.

Use it to monitor production metrics, review logs and uptime, detect regressions, and escalate fixes when thresholds are breached.

It helps identify problems after deployment, when changes are running in the real system.

sparc-post-deployment-monitoring-mode — Command for Claude Code by f-a

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/f-amine/vibe-stack

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/f-amine/vibe-stack/post-deployment-monitoring-mode/github.svg)](https://agentmods.dev/commands/f-amine/vibe-stack/post-deployment-monitoring-mode)

Your own site

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

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

When invoked 614 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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.00614
Opus 5	$0.00017	$0.00307
Sonnet 5	$0.00007	$0.00123
Haiku 4.5	$0.00003	$0.00061

Measured 7d ago against content hash f112e0fd1d1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 7d 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.

Origin

This is a copy

100% identical to sparc-post-deployment-monitoring-mode — 0 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/post-deployment-monitoring-mode.md · 84 lines

How it starts

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

📈 Deployment Monitor

Role Definition

You observe the system post-launch, collecting performance, logs, and user feedback. You flag regressions or unexpected behaviors.

Custom Instructions

Configure metrics, logs, uptime checks, and alerts. Recommend improvements if thresholds are violated. Use new_task to escalate refactors or hotfixes. Summarize monitoring status and findings with attempt_completion.

Available Tools

read: File reading and viewing
edit: File modification and creation
browser: Web browsing capabilities
mcp: Model Context Protocol tools
command: Command execution

Usage

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

mcp__claude-flow__sparc_mode {
  mode: "post-deployment-monitoring-mode",
  task_description: "monitor production metrics",
  options: {
    namespace: "post-deployment-monitoring-mode",
    non_interactive: false
  }
}

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

# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run post-deployment-monitoring-mode "monitor production metrics"

# For alpha features
npx claude-flow@alpha sparc run post-deployment-monitoring-mode "monitor production metrics"

# With namespace
npx claude-flow sparc run post-deployment-monitoring-mode "your task" --namespace post-deployment-monitoring-mode

# Non-interactive mode
npx claude-flow sparc run post-deployment-monitoring-mode "your task" --non-interactive

Option 3: Local Installation

# If claude-flow is installed locally
./claude-flow sparc run post-deployment-monitoring-mode "monitor production metrics"

Memory Integration

Using MCP Tools (Preferred)

// Store mode-specific context
mcp__claude-flow__memory_usage {
  action: "store",
  key: "post-deployment-monitoring-mode_context",
  value: "important decisions",
  namespace: "post-deployment-monitoring-mode"
}

// Query previous work
mcp__claude-flow__memory_search {
  pattern: "post-deployment-monitoring-mode",
  namespace: "post-deployment-monitoring-mode",
  limit: 5
}

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

7d ago First seen · 84 lines · 34 tokens per session scan A f112e0fd1d1b

Subscribe to this mod's changes

sparc-post-deployment-monitoring-mode is a command published in the GitHub repository f-amine/vibe-stack (21 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 614 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sparc-post-deployment-monitoring-mode, differing in 0 lines, and is treated as a copy.

Analytics and metrics Claude Code Cloud DevOps and cloud ai better-auth claude drizzle-orm nextjs

sparc-post-deployment-monitoring-mode