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.
curl -O https://raw.githubusercontent.com/williamzujkowski/standards/master/.claude/commands/sparc/post-deployment-monitoring-mode.mdgit clone --depth 1 https://github.com/williamzujkowski/standardsWrote 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/williamzujkowski/standards/post-deployment-monitoring-mode)<a href="https://agentmods.dev/commands/williamzujkowski/standards/post-deployment-monitoring-mode"><img src="https://agentmods.dev/badge/commands/williamzujkowski/standards/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.
<a href="https://agentmods.dev/commands/williamzujkowski/standards/post-deployment-monitoring-mode"><img src="https://agentmods.dev/badge/commands/williamzujkowski/standards/post-deployment-monitoring-mode.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.00034 | $0.00614 |
| Opus 5.5 | $0.00014 | $0.00246 |
| Sonnet 5.5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
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 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.
This is a copy
100% identical to sparc-post-deployment-monitoring-mode — 8 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.
How it starts
The opening of the file, as written. The whole thing — 92 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
}
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.
- yesterday First seen · 92 lines · 34 tokens per session scan A ec464c677616
sparc-post-deployment-monitoring-mode is a command published in the GitHub repository williamzujkowski/standards (18 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 614 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-post-deployment-monitoring-mode, differing in 8 lines, and is treated as a copy.
Other commands, from other repositories
cost-optimize
Reduce cloud costs across AWS, Azure, and GCP through rightsizing, reserved and spot capacity, storage tuning, and cost monitoring.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
Set up third-party service integrations.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.