sparc-post-deployment-monitoring-mode

sparc-post-deployment-monitoring-mode is a command for Claude Code from ruvnet/RuView. It costs 34 tokens per session (614 once invoked), scanned A, original, MIT.

A post-launch monitoring command that watches system performance, logs, uptime, and user feedback for unexpected behaviour.

In plain words
What is it for?
Use it to monitor a live system, check configured thresholds, flag problems, and suggest follow-up fixes.
Why use it?
It helps you notice regressions—new problems introduced after a release—and other production issues sooner.

Command for Claude Code

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

Good fit Use it to monitor a live system, check configured thresholds, flag problems, and suggest follow-up fixes.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ruvnet/ruview/post-deployment-monitoring-mode
About the project

RuView is a WiFi sensing platform that uses disturbances in radio signals, captured by low-cost ESP32 sensors, to detect presence, movement, breathing, and heart rate without cameras or wearables. It is intended for spatial monitoring and smart-home integrations. The catalogue add-ons support workflows for operating and integrating RuView.

ruvnet/RuView · 92,962 stars · on GitHub · cognitum.one

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/ruvnet/RuView

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-post-deployment-monitoring-mode

README.md
[![agentmods](https://agentmods.dev/badge/commands/ruvnet/ruview/post-deployment-monitoring-mode/github.svg)](https://agentmods.dev/commands/ruvnet/ruview/post-deployment-monitoring-mode)
Your own site
<a href="https://agentmods.dev/commands/ruvnet/ruview/post-deployment-monitoring-mode"><img src="https://agentmods.dev/badge/commands/ruvnet/ruview/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.

agentmods 80×15 button for sparc-post-deployment-monitoring-mode

Your own site · 80×15
<a href="https://agentmods.dev/commands/ruvnet/ruview/post-deployment-monitoring-mode"><img src="https://agentmods.dev/badge/commands/ruvnet/ruview/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 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.

ModelPer sessionOnce 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 8d 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 8d 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

Copies of this mod

8 near-identical copies found in the catalogue:

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

  1. 8d 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 ruvnet/RuView (92,962 stars, last pushed yesterday), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.