p7-deploy

p7-deploy is a command for Claude Code from jonase47/ccpr. It costs 0 tokens per session (1,378 once invoked), scanned A, original, MIT.

A deployment command that releases software to a specified environment and runs smoke tests afterward. Smoke tests are quick checks that the main parts of a system still work.

In plain words
What is it for?
Use it to deploy to staging or production and confirm basic operation with post-deployment checks.
Why use it?
It verifies the release after deployment instead of treating the upload as proof that the system is running correctly. It also checks that preparation and approval steps were completed first.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths.

Good fit Use it to deploy to staging or production and confirm basic operation with post-deployment checks.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/jonase47/ccpr/p7-deploy
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.

Clone the repo
git clone --depth 1 https://github.com/jonase47/ccpr

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/jonase47/ccpr/p7-deploy/github.svg)](https://agentmods.dev/commands/jonase47/ccpr/p7-deploy)
Your own site
<a href="https://agentmods.dev/commands/jonase47/ccpr/p7-deploy"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p7-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 p7-deploy

Your own site · 80×15
<a href="https://agentmods.dev/commands/jonase47/ccpr/p7-deploy"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p7-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,378 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.00000 $0.01378
Opus 5.5 $0.00000 $0.00551
Sonnet 5.5 $0.00000 $0.00276
Haiku 4.5 $0.00000 $0.00138

Measured 1mo ago against content hash 9a623c86b948, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

p7-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 1mo 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.

commands/p7-deploy.md · 118 lines

How it starts

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

/p7-deploy – Execute Deployment & Smoke Tests

Executes the deployment to the target environment and then verifies with smoke tests that the system is running correctly. Only when the smoke tests pass is the deployment considered successful.

Argument: $ARGUMENTS = [Environment, e.g. "staging", "production"]

If provided: Deploy to the specified environment. If not provided: Ask for the target environment. Without a clear specification, do not start the deployment – the environment is critical information.

Execution

1. Read Context and Check Prerequisites

Read the following files (if available):

  • PREPARE.md (has the preparation from /p7-prepare been completed?)
  • INFRASTRUCTURE.md (deployment procedure, rollback strategy)
  • GATE_P6.md (approval status)

Mandatory checks before deployment:

  • Does PREPARE.md exist with a completed checklist? If not → stop, recommend /p7-prepare first.
  • Is Gate 6 approved with green or yellow? If not → stop.

2. Delegation to DevOps Agent (Lead)

Delegate the deployment to the devops agent:

Execute the deployment to the following environment: $ARGUMENTS Deployment procedure from INFRASTRUCTURE.md and PREPARE.md: [Apply procedure]

A. Execute Deployment Execute the deployment step by step and document each step:

  1. Activate maintenance mode (if no zero-downtime deployment)
  2. Execute database migrations
  3. Deploy new application version
  4. Restart services / switch traffic
  5. Deactivate maintenance mode Log timestamp and result for each step.

B. Smoke Tests Immediately after deployment, verify the most critical system functions:

  • Is the application reachable? (HTTP 200 on the home page)
  • Does authentication work? (Login successful)
  • Is the database connection active? (Health endpoint or simple DB query)
  • Does the most critical core workflow work? (1 E2E smoke test)
  • Are external services reachable? (email, payment, etc.)
  • Are monitoring and logging running? (Logs appear, metrics are collected)

C. Immediate Rollback on Smoke Test Failure If a smoke test fails:

  1. Immediately initiate rollback (according to the rollback plan from PREPARE.md)
  2. Document the failure
  3. Mark deployment as failed
  4. Analyse the cause before the next deployment attempt

Read the full file on GitHub · 118 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. 1mo ago Changed · +3 lines 9a623c86b948
  2. 2mo ago Changed 141785490a36
  3. 2mo ago First seen · 115 lines · 0 tokens per session scan A d07395c38159

Subscribe to this mod's changes

p7-deploy is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,378 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-09-03.

Related

p7-deploy compared with commands from other repositories

p7-deploy next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
p7-deployjonase47/ccprCommand11mo agoMITA0Claude Code
firebase-publishPierry/harness-kitCommand41mo agoMITA20Claude Code
statsAR6420/Hail_HydraCommand517d agoMITA29Claude Code
debugjoaquimscosta/arkhe-claude-pluginsCommand2223d agoMITA48Claude Code
forge-compact-taskluiseiman/dotforgeCommand83d agoMITA46Claude Code
forge-resetluiseiman/dotforgeCommand83d agoMITA15Claude Code
_conventionsbuild-with-dhiraj/ai-workflow-framework-portability-kitCommand51mo agoMITA0Claude Code