What is pn-ci-dev-prod-split?

A CI setup that keeps development and production deployments separate. CI means automated checks and delivery; production is the live environment used by customers.

Use it when creating or refactoring deployment workflows so development deploys automatically while production requires a manual trigger.

It prevents a normal code push from deploying straight to production and keeps development and production settings and secrets apart.

pn-ci-dev-prod-split — Skill for Cursor by perniemann

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 perniemann/pnCore --skill pn-ci-dev-prod-split

Clone the repo

git clone --depth 1 https://github.com/perniemann/pnCore

Made for: Cursor.

Or install pn-core, the plugin that ships this one along with the rest of its 133 skills, 19 commands, 9 agents, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/perniemann/pncore/pn-ci-dev-prod-split.svg)](https://agentmods.dev/skills/perniemann/pncore/pn-ci-dev-prod-split)

Your own site

<a href="https://agentmods.dev/skills/perniemann/pncore/pn-ci-dev-prod-split"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-ci-dev-prod-split.svg" alt="Measured on agentmods" height="20"></a>

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 605 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.

Model	Per session	Once invoked
Fable 5.1	$0.00055	$0.00605
Opus 5	$0.00028	$0.00302
Sonnet 5	$0.00011	$0.00121
Haiku 4.5	$0.00006	$0.00060

Measured 4d ago against content hash 0a21856561b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

pn-ci-dev-prod-split 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 4d 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.

packages/pn-core-mcp/content/skills/ci/pn-ci-dev-prod-split/SKILL.md · 44 lines

How it starts

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

CI dev/prod split

When to use

Scaffolding CI for a new project
Adding deploy workflows to an existing repo
User asks for "dev and prod" or "staging vs production" CI
Fixing or refactoring workflows that merge dev/prod in one file

Pattern

Workflow	Trigger	Concurrency	Deploy target
deploy-dev	push to main (or develop), paths-ignore	cancel-in-progress: true	Dev path/env
deploy-prod	workflow_dispatch only	cancel-in-progress: false	Prod path/env
*-test (optional)	workflow_dispatch	—	Tests dev + prod connectivity

Principles: Dev auto-deploys on push; prod is manual-only; separate env vars (e.g. PUBLIC_ENV=development vs production); separate paths/secrets (DEV_, PROD_).

Instructions

Separate workflows: Create deploy-dev.yml and deploy-prod.yml (not one workflow with branch condition).
Dev workflow: Trigger on push to main (or develop). Use paths-ignore for non-code changes (e.g. README, .cursorrules). Build with PUBLIC_ENV=development or equivalent.
Prod workflow: Trigger on workflow_dispatch only. Never auto-deploy to prod. Build with PUBLIC_ENV=production or equivalent. Use environment: production in GitHub for optional approval gates.
Concurrency: Dev: cancel-in-progress: true (new push cancels in-flight deploy). Prod: cancel-in-progress: false (do not cancel prod deploy).
Deploy target adapters:
- FTP: DEV_FTP_PATH vs PROD_FTP_PATH; separate .htaccess (dev: password protect; prod: security headers)
- Vercel: Preview = dev; Production = prod; use env vars per environment
- Netlify: Branch deploys = dev; Production = prod
- Cloudflare Pages: Preview = dev; Production = prod
Optional test workflow: Manual workflow to verify deploy connectivity (e.g. ftp-test for FTP) for both dev and prod paths.
Reference pn-ci: For secrets (never in YAML), action pinning, caching. Keep workflows minimal.

Read the full file on GitHub · 44 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.

4d ago First seen · 44 lines · 55 tokens per session scan A 0a21856561b9

Subscribe to this mod's changes

pn-ci-dev-prod-split is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 605 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-09-03.

CI and CD DevOps and cloud LLM TypeScript agents cursor mcp plugin

github-actions-templates

Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.

wshobson/agents · 44 tokens

secrets-management

Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.

wshobson/agents · 39 tokens

deployment-pipeline-design

Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.

wshobson/agents · 58 tokens

pn-ci-dev-prod-split