deploy-local

deploy-local is a skill for Claude Code, Codex from saajunaid/caddis-plugin. It costs 45 tokens per session (2,431 once invoked), scanned A, original, MIT.

A local deployment workflow for projects hosted on Gitea, a self-hosted Git service. It covers the path from committing code through CI, deployment, production checks, and fixes.

In plain words
What is it for?
Use it to commit on a development branch, push to Gitea, monitor the build and deployment workflow, validate the production host, and repair failures.
Why use it?
It brings the repeated steps of deploying to a local production setup into one process and helps find build, lint, test, or pipeline failures.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to commit on a development branch, push to Gitea, monitor the build and deployment workflow, validate the production host, and repair failures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/saajunaid/caddis-plugin/deploy-local
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 saajunaid/caddis-plugin --skill deploy-local
Clone the repo
git clone --depth 1 https://github.com/saajunaid/caddis-plugin

Made for: Claude Code, Codex.

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 deploy-local

README.md
[![agentmods](https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/deploy-local/github.svg)](https://agentmods.dev/skills/saajunaid/caddis-plugin/deploy-local)
Your own site
<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/deploy-local"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/deploy-local/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 deploy-local

Your own site · 80×15
<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/deploy-local"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/deploy-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,431 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.00045 $0.02431
Opus 5.5 $0.00018 $0.00972
Sonnet 5.5 $0.00009 $0.00486
Haiku 4.5 $0.00005 $0.00243

Measured 11d ago against content hash b5c44e845d25, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deploy-local 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 11d 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.

.github/skills/devops/deploy-local/SKILL.md · 261 lines

How it starts

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

Deploy Local Skill

Run reliable local-to-prod delivery for repositories hosted on a self-hosted Gitea.

When To Use

Use this skill when requests include any of:

  • "commit and deploy"
  • "commit and push"
  • "push and monitor pipeline"
  • "watch prod deploy"
  • "monitor deployment in prod"
  • "fix CI failures"
  • "lint/test failing in pipeline"
  • "stuck in queue"

Required Companion Skills

Load these first when they exist (your org may ship private deploy skills):

  • your org's golden-workflow skill (CI/CD workflow contract)
  • your org's windows-deployment skill (NSSM + reverse proxy)
  • .github/skills/devops/ci-cd-pipeline/SKILL.md
  • .github/skills/devops/git-commit/SKILL.md

Optional:

  • .github/skills/devops/gh-cli/SKILL.md for issue/PR linking
  • .github/skills/workflow/verification-loop/SKILL.md for stricter local validation loops

Local Platform Defaults (configure per project)

Resolve these from your project config (e.g. a repo-local config/.env.gitea) — do not hardcode:

  • Gitea UI / API base: $env:GITEA_BASE_URL (e.g. http://gitea.example:8090, API at .../api/v1)
  • Repo org/owner: <org>
  • Expected non-prod runner label: dev
  • Expected prod runner label: prod
  • Prod host: $env:PROD_HOST
  • Prod checkout root: <prod-checkout-root>\<repo>

Golden Deploy Model

The deploy-critical path is SHA-driven:

  1. A push to main triggers the canonical .gitea/workflows/ci.yml.
  2. lint_and_test and any repo-relevant frontend checks run on dev.
  3. deploy_prod runs on prod only after gates pass.
  4. Prod fetches, resets, and verifies the expected commit SHA.
  5. Prod installs/builds/restarts app-owned NSSM services.
  6. Prod health and version endpoints are verified.
  7. release_metadata creates/pushes the CalVer Git tag only after deploy success.
  8. A tag-triggered workflow run may occur, but deploy/release jobs must be skipped for tag refs.

CalVer is release metadata, not the deploy identity. Do not reintroduce tag-first deploy logic.

Read the full file on GitHub · 261 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. 11d ago Changed · +1 lines b5c44e845d25
  2. 1mo ago Changed · -15 tokens per session 12ec10e1ce2e
  3. 1mo ago First seen · 260 lines · 60 tokens per session scan A 4729465da1f3

Subscribe to this mod's changes

deploy-local is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 2,431 once invoked, about $0.0002 per session on Opus 5.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-09-03.