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.
curl -O https://raw.githubusercontent.com/SumoLogic/sumologic-documentation/main/.claude/commands/review-teardown.mdgit clone --depth 1 https://github.com/SumoLogic/sumologic-documentationWrote 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/sumologic/sumologic-documentation/review-teardown)<a href="https://agentmods.dev/commands/sumologic/sumologic-documentation/review-teardown"><img src="https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/review-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.
<a href="https://agentmods.dev/commands/sumologic/sumologic-documentation/review-teardown"><img src="https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/review-teardown.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.00000 | $0.00356 |
| Opus 5.5 | $0.00000 | $0.00142 |
| Sonnet 5.5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
review-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.
What it actually says
Review Teardown — Remove a Review Deployment
Delete a review branch to free the shared Pantheon review slot.
When to use this command
- Article review is complete and the review branch is no longer needed.
- A PR was closed or merged and the review slot should be cleared for the next deployment.
Usage
/review-teardown {pr-number-or-branch}
Examples:
/review-teardown 6701/review-teardown docs-update-jira-skill-fields
Workflow
Step 1: Resolve to review branch name
- If input is numeric: review branch is
review/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 usereview/pr-{number}.
Step 2: Verify the branch exists
git ls-remote --heads origin refs/heads/review/pr-{number}
If the branch is not found, inform the user and exit — nothing to delete.
Step 3: Delete the review branch
git push origin --delete review/pr-{number}
Step 4: Post PR comment
Post a comment on the PR confirming the review branch was deleted and noting that the review 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_URLwebhook, or any Slack bot token, from GitHub Actions secrets — secrets are write-only once set. The PR comment in Step 4 covers coordination instead.
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 · 48 lines · 0 tokens per session scan A f03dcafdedce
review-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 356 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.
review-teardown compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| review-teardownSumoLogic/sumologic-documentation | Command | 42 | yesterday | MIT | A | 0 | Claude Code |
| pr-readycostajohnt/oss-autopilot | Command | 26 | 4d ago | MIT | A | 45 | Claude Code |
| prepare-releasesaeedkolivand/ai-job-hunter-app | Command | 63 | yesterday | Apache-2.0 | A | 20 | Claude Code |
| review-diffChatbotXIO/ChatbotX | Command | 1.1k | yesterday | none | A | 26 | Claude Code |
| review-fixesChatbotXIO/ChatbotX | Command | 1.1k | yesterday | none | A | 19 | Claude Code |
| speckit.spex.submitrhuss/cc-spex | Command | 122 | 3d ago | Apache-2.0 | A | 15 | Claude Code |
| gitazrtydxb/procoder | Command | 211 | 11d ago | Apache-2.0 | A | 20 | Claude Code |