manual-only-deploy

manual-only-deploy is a skill for Claude Code from davila7/claude-with-skills. It costs 22 tokens per session (505 once invoked), scanned A, original, MIT.

A controlled procedure for deploying an application to production. It checks the Git working tree, tests, build, version, and release tag before pushing that tag to the remote repository.

In plain words
What is it for?
Use it manually when preparing a production release that must pass checks and receive a dated version tag.
Why use it?
It stops the deployment when local changes, failing tests, or a failed build could make the release unsafe.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it manually when preparing a production release that must pass checks and receive a dated version tag.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/davila7/claude-with-skills/manual-only-deploy
About the project

Claude With Skills is a progressive course that teaches developers to create reusable, portable Agent Skills for Claude Code, from basic SKILL.md files to advanced automation and plugin packaging. It is intended for developers who want repeatable instructions and workflows instead of repeatedly pasting the same guidance. The catalogue contains the course's skills, agents, and instruction.

davila7/claude-with-skills · 12 stars · on GitHub · claude-with-skills.vercel.app

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 davila7/claude-with-skills --skill manual-only-deploy
Clone the repo
git clone --depth 1 https://github.com/davila7/claude-with-skills

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 manual-only-deploy

README.md
[![agentmods](https://agentmods.dev/badge/skills/davila7/claude-with-skills/manual-only-deploy/github.svg)](https://agentmods.dev/skills/davila7/claude-with-skills/manual-only-deploy)
Your own site
<a href="https://agentmods.dev/skills/davila7/claude-with-skills/manual-only-deploy"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/manual-only-deploy/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 manual-only-deploy

Your own site · 80×15
<a href="https://agentmods.dev/skills/davila7/claude-with-skills/manual-only-deploy"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/manual-only-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 505 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.00022 $0.00505
Opus 5 $0.00011 $0.00253
Sonnet 5 $0.00004 $0.00101
Haiku 4.5 $0.00002 $0.00051

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

Security

Grade A, and why

manual-only-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 12d 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.

src/content/docs/02-intermediate/lesson-02-invocation-control/examples/manual-only-deploy/SKILL.md · 79 lines

What it actually says

Deploy workflow

This skill deploys the application. It runs a series of checks before touching anything remote. If any step fails, it stops immediately and reports the failure. It does not retry automatically.

Step 1: Confirm no uncommitted changes

Run:

git status

If the output shows modified or untracked files, stop here. Report: "Deploy aborted: there are uncommitted changes. Commit or stash them before deploying." Do not proceed.

Step 2: Run the test suite

Run:

npm test

If any test fails, stop here. Report which tests failed and do not proceed.

Step 3: Build the project

Run:

npm run build

If the build fails, stop here. Report the error output and do not proceed.

Step 4: Create a version tag

Read the current version from package.json:

cat package.json

Extract the version field. Create a git tag in the format v<version>-<YYYYMMDD>:

git tag v<version>-<YYYYMMDD>

For example, if the version is 2.3.1 and today is 2026-05-13, the tag is v2.3.1-20260513.

If a tag with that name already exists, append a counter: v2.3.1-20260513-2.

Step 5: Push the tag

Run:

git push origin <tag-name>

If the push fails, report the error. Do not retry.

Step 6: Report completion

Print a summary:

  • Tag name
  • Commit SHA the tag points to (git rev-parse HEAD)
  • Timestamp

Example output:

Deploy complete.
Tag: v2.3.1-20260513
Commit: a1b2c3d4e5f6
Time: 2026-05-13 14:32:07 UTC
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. 12d ago First seen · 79 lines · 22 tokens per session scan A 429df8eaf408

Subscribe to this mod's changes

manual-only-deploy is a skill published in the GitHub repository davila7/claude-with-skills (12 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 505 once invoked, about $0.0001 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-30.