agentmods.dev

sumologic-documentation: Command for Claude Code

.claude/commands/stage-teardown.md

stage-teardown is a command for Claude Code from SumoLogic/sumologic-documentation. It costs 0 tokens per session (359 once invoked), scanned A, original, MIT.

A command that deletes a staging branch from Pantheon, a website hosting service, after a pull request is finished. It also confirms the deletion on the pull request.

In plain words
What is it for?
Use it after external review, or when a pull request is closed or merged. Give it a pull request number or branch name.
Why use it?
It frees the shared staging slot for another deployment and avoids leaving unused staging branches behind.

Command for Claude Code

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

This is SumoLogic/sumologic-documentation's own configuration. It tells Claude Code how to work on sumologic-documentation 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 sumologic-documentation configures →

not rated 42repo yesterday A scan 0 tokens original MIT
View source ↗ SumoLogic/sumologic-documentation sumologic.com
Reuse

Borrowing it

Nothing to install: this file belongs to SumoLogic/sumologic-documentation. 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/SumoLogic/sumologic-documentation/main/.claude/commands/stage-teardown.md
Clone the repo
git clone --depth 1 https://github.com/SumoLogic/sumologic-documentation

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 stage-teardown

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/sumologic/sumologic-documentation/stage-teardown"><img src="https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/stage-teardown.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 359 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.00000 $0.00359
Opus 5.5 $0.00000 $0.00144
Sonnet 5.5 $0.00000 $0.00072
Haiku 4.5 $0.00000 $0.00036

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

Security

Grade A, and why

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

.claude/commands/stage-teardown.md · 48 lines

What it actually says

Stage Teardown — Remove a Staging Deployment

Delete a staging branch to free the shared Pantheon staging slot.

When to use this command

  • External review is complete and the staging branch is no longer needed.
  • A PR was closed or merged and the staging slot should be cleared for the next deployment.

Usage

/stage-teardown {pr-number-or-branch}

Examples:

  • /stage-teardown 6701
  • /stage-teardown docs-update-jira-skill-fields

Workflow

Step 1: Resolve to staging branch name

  • If input is numeric: staging branch is staging/pr-{number}.
  • If input is a branch name: look up the PR number with gh pr list --head {branch} --json number --jq '.[0].number', then use staging/pr-{number}.

Step 2: Verify the branch exists

git ls-remote --heads origin refs/heads/staging/pr-{number}

If the branch is not found, inform the user and exit — nothing to delete.

Step 3: Delete the staging branch

git push origin --delete staging/pr-{number}

Step 4: Post PR comment

Post a comment on the PR confirming the staging branch was deleted and noting that the staging URL may still serve the old build until the next deployment.

Limitations

  • No Slack notifications from this command: out of scope. Claude Code running locally can't read the WEBOPS_SLACK_URL webhook, or any Slack bot token, from GitHub Actions secrets — secrets are write-only once set. The PR comment in Step 4 covers coordination instead.
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. 2mo ago First seen · 48 lines · 0 tokens per session scan A 49ad752587fc

Subscribe to this mod's changes

stage-teardown is a command published in the GitHub repository SumoLogic/sumologic-documentation (42 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 359 tokens. 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-30.

Git and workflowReactdocumentationopen-source
Related

stage-teardown compared with commands from other repositories

stage-teardown next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
stage-teardownSumoLogic/sumologic-documentationCommand42yesterdayMITA0Claude Code
implement-featureHoangNguyen0403/agent-skills-standardCommand583yesterdayMITA0Claude Code
session-reporttdimino/claude-code-minoanCommand41yesterdayMITA0Claude Code
pr-readycostajohnt/oss-autopilotCommand264d agoMITA45Claude Code
releasejezweb/claude-skillsCommand1.1k28d agoMITB7Claude Code
prepare-releasesaeedkolivand/ai-job-hunter-appCommand63yesterdayApache-2.0A20Claude Code
deployNickRomanek/clawbridgeCommand2319d agoApache-2.0A0Claude Code