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.
npx agentmods add commands/sumologic/sumologic-documentation/stage-deploygit clone --depth 1 https://github.com/SumoLogic/sumologic-documentationWhat 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 | $0.00000 | $0.01383 |
| Opus 5 | $0.00000 | $0.00691 |
| Sonnet 5 | $0.00000 | $0.00277 |
| Haiku 4.5 | $0.00000 | $0.00138 |
Grade A, and why
stage-deploy 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage Deploy — Deploy PR to Shared Staging
Deploy a PR branch to the shared Pantheon staging environment for previewing UX/UI changes or other site-wide feature work before merge.
When to use this command
- You're shipping a UX/UI change, new Docusaurus feature, or other site-wide update and need a live environment to validate it before merge.
- A reviewer needs to see the change in context (navigation, theming, layout) rather than as a single article.
For quick, temporary article-level review, use /review-deploy instead — it targets the separate docs-review environment and keeps this slot free for feature work.
Usage
/stage-deploy {pr-number-or-branch}
Examples:
/stage-deploy 6701/stage-deploy docs-update-jira-skill-fields
Staging environment
- URL:
https://helpdocs-sumo-logic.pantheonsite.io/help/ - HTTP basic auth protected: Contact the docs team for credentials.
- Single shared slot: Only one PR can be staged at a time. Deploying overwrites the previous deployment.
- Build time: 5–10 minutes after the push triggers the workflow.
Workflow
Step 1: Resolve input to PR number
- If input is numeric: validate the PR exists and is open with
gh pr view {number} --json state --jq '.state'. - If input is a branch name: look up the PR number with
gh pr list --head {branch} --json number --jq '.[0].number'.
You need the PR number for the staging branch name, the PR comment, and to fetch the PR's head commit in Step 4. The branch name itself isn't needed for the push — see Step 4 for why.
Step 2: Check for conflicts
git ls-remote --heads origin 'refs/heads/staging/pr-*'
Exclude staging/pr-{number} for the PR you're currently deploying from the results — redeploying the same PR after new commits isn't a conflict with itself, and shouldn't trigger the overwrite comment below on the PR's own thread.
If one or more other staging branches remain, identify who owns each one (gh pr view {n} for every match) and list all of them for the user:
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 · 113 lines · 0 tokens per session scan A 6d9f85a30f3d
stage-deploy is a command published in the GitHub repository SumoLogic/sumologic-documentation (42 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,383 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.
Other commands, from other repositories
add-scaffold
按 14-phase 工作流为指定 app 编写清理 scaffold（含需求采集、实测勘测、TOML、safety test、UI 集成）.
scaffold-review
Command "scaffold-review" from cccyd2003-qwq/pinkbin, covering 诊断 checklist, phase 1-2 类别需求, phase 5-7 实测勘测, phase 8 toml 本身 and phase 10 safety test.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
loci-scan
Refresh the current project's local Loci memory.
adr-supersede
Create a new ADR that supersedes an existing one.
spec-forge
Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.