deploying-to-staging-environment

deploying-to-staging-environment is a skill for Claude Code from gabrielmoreira/agent-skills-mirror. It costs 44 tokens per session (2,929 once invoked), scanned A, a copy of deploying-to-staging-environment, MIT.

A deployment procedure for sending coordinated changes from three related repositories to a staging environment. Staging is a test copy used to verify changes before production, and GitHub Actions is the automation service that runs the deployment steps.

In plain words
What is it for?
Use it to sync feature branches across the relay, relay-dashboard and relay-cloud repositories, trigger staging deployment and verify integrated changes.
Why use it?
It keeps branches and cross-repository changes aligned when one feature spans several codebases. It provides a shared place to test the combined result without changing the production system.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to sync feature branches across the relay, relay-dashboard and relay-cloud repositories, trigger staging deployment and verify integrated changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gabrielmoreira/agent-skills-mirror/deploying-to-staging-environment
Install

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.

Any agent
npx skills add gabrielmoreira/agent-skills-mirror --skill deploying-to-staging-environment
Clone the repo
git clone --depth 1 https://github.com/gabrielmoreira/agent-skills-mirror

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 deploying-to-staging-environment

README.md
[![agentmods](https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/deploying-to-staging-environment/github.svg)](https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/deploying-to-staging-environment)
Your own site
<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/deploying-to-staging-environment"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/deploying-to-staging-environment/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 deploying-to-staging-environment

Your own site · 80×15
<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/deploying-to-staging-environment"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/deploying-to-staging-environment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,929 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00044 $0.02929
Opus 5 $0.00022 $0.01465
Sonnet 5 $0.00009 $0.00586
Haiku 4.5 $0.00004 $0.00293

Measured 6d ago against content hash 16f1f86eba0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

deploying-to-staging-environment scanned grade A with 1 finding 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 6d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Workflow runs `curl https://agent-relay-staging.fly.dev/health`
Origin

This is a copy

100% identical to deploying-to-staging-environment — 0 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.

mirrors/repos/AgentWorkforce@relay/.claude/skills/deploying-to-staging-environment/SKILL.md · 397 lines

How it starts

The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deploying to Staging Environment

Overview

The staging environment deployment is a coordinated multi-repo process that synchronizes code across three repositories (relay, relay-dashboard, relay-cloud) and automatically triggers deployment via GitHub Actions. Staging deployments ensure feature verification before production while keeping main branch clean during development.

When to Use

  • Integrating features across repos - Multiple components depend on changes in different repos
  • Testing feature branches together - Verify feature branch changes don't break integration
  • Promoting main to staging - Standard sync to keep staging up-to-date with latest main
  • Verifying deployment readiness - Test infrastructure changes or deployment workflows
  • Cross-team coordination - Share feature branches for integration testing

When NOT to use:

  • Emergency hotfixes (use production deployment instead)
  • Single-repo changes only (push directly if not blocking other repos)
  • Testing without intent to deploy (use local environment instead)

Architecture

The staging deployment system consists of:

Three Repos (relay, relay-dashboard, relay-cloud)
    ↓
Staging Branches (synced via git push)
    ↓
relay-cloud staging push triggers GitHub Actions
    ↓
Deploy-Staging Workflow (deploy-staging.yml)
    ↓
Fly.io Staging Environment (agent-relay-staging)
    ↓
Automatic health check verification

Key details:

  • Each repo has independent staging branch
  • relay-cloud staging branch push triggers automatic deployment
  • Workflow accepts optional relay/dashboard branch overrides
  • Falls back to main if specified branch doesn't exist
  • Workspace image builds in parallel with API deployment

Quick Reference

Standard Workflow (All Repos)

# 1. Create git worktree for staging work (BEST PRACTICE)
cd /data/repos/relay
git worktree add .worktrees/staging-push main
cd .worktrees/staging-push

# 2. Push latest main to staging (fetch fresh)
git fetch origin main:main
git push origin main:staging

# 3. Or push current feature branch to staging (if desired)
git fetch origin feature/your-branch:feature/your-branch
git push origin feature/your-branch:staging

# 4. Clean up worktree
cd /data/repos/relay
git worktree remove .worktrees/staging-push

Read the full file on GitHub · 397 lines

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. 6d ago First seen · 397 lines · 44 tokens per session scan A 16f1f86eba0d

Subscribe to this mod's changes

deploying-to-staging-environment is a skill published in the GitHub repository gabrielmoreira/agent-skills-mirror (17 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 2,929 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to deploying-to-staging-environment, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

baby-sit

Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.

langchain-ai/open-swe · 30 tokens

atmos-hooks

Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.

cloudposse/atmos · 46 tokens

atmos-pro

Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.

cloudposse/atmos · 38 tokens

pr-watch

Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.

SethGammon/Citadel · 46 tokens

start-temps-cluster

Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + temps agent, wired with the real multi-host overlay (VXLAN, computecidr allocation) via tools/dev-cluster/ in whichever checkout/worktree you run…

gotempsh/temps · 204 tokens