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 skills/evolplus/talos/staging-deploymentnpx skills add evolplus/talos --skill staging-deploymentgit clone --depth 1 https://github.com/evolplus/talosWhat 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.00058 | $0.00754 |
| Opus 5 | $0.00029 | $0.00377 |
| Sonnet 5 | $0.00012 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
staging-deployment 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staging Deployment
When to use
Use this skill when a DevOps task targets staging, testing, UAT, pre-prod, or any shared non-local environment. Local QA deploys still use local-deployment; this skill governs promotion into an environment other people depend on.
Inputs and outputs
- Inputs: task ID, target environment, approved build/image/version, deployment mechanism, release-readiness evidence, rollback plan, environment config contract, and access method.
- Outputs: staging deploy report, smoke-test evidence, target URLs, rollout/rollback command references, and follow-up issues for failed gates.
Procedure
- Confirm target and approval. Verify the task explicitly names the staging environment and version/build to deploy. If the target is ambiguous, halt with
NEEDS_CONTEXT. - Run release gates first. Consult
release-readiness; do not deploy if release readiness, migration safety, rollback readiness, secrets/config audit, or observability readiness is incomplete. - Select execution path. Use
ssh-remote-operations,docker-deployment, orkubernetes-deploymentdepending on the target. Reference credential files only as command inputs. - Freeze the deploy input. Record commit SHA, image tag/digest, migration version, config version, and artifact checksum where available. Do not deploy mutable
latestunless the task has an approved exception. - Deploy in a bounded scope. Touch only the named environment, namespace, host alias, compose project, or service set. Avoid broad cluster/host operations.
- Run staging smoke checks. Verify health endpoints, required background workers, migrations, critical user flows, and external dependency connectivity using non-production fixtures.
- Capture rollback evidence. Record previous version, rollback command, rollback owner, expected data constraints, and whether rollback was tested or only prepared.
- Write the deploy report. Include environment, version, deploy mechanism, validation results, smoke checks, URLs, known limitations, and redacted config status.
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.
- 3d ago First seen · 47 lines · 58 tokens per session scan A e53e6c63e301
staging-deployment is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 29d ago), licensed Apache-2.0. It adds 58 tokens to every session and 754 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
dsh-web-pre-push-checks
Use before pushing, opening or updating a pull request, or claiming dsh-web checks pass. Selects the required repository gates and diff-specific generation, build, and GUI evidence.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
harness-setup
HAR: Project init, tool setup, agent config, memory setup, skill mirror sync. Trigger: setup, init, new project, CI/Codex setup, harness-mem, mirror. Do NOT load for: implementation, review, release, planning.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.