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.
npx agentmods add skills/shandar/pwp-plugin/pwp-deploynpx skills add shandar/pwp-plugin --skill pwp-deploygit clone --depth 1 https://github.com/shandar/pwp-pluginWhat 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 | $0.00119 | $0.01262 |
| Opus 5 | $0.00060 | $0.00631 |
| Sonnet 5 | $0.00024 | $0.00252 |
| Haiku 4.5 | $0.00012 | $0.00126 |
Grade A, and why
pwp-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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PWP Deployment Protocol
You are now operating under the Project Workflow Protocol's deployment discipline. Follow this structured approach for every deployment task.
Context: $ARGUMENTS
Phase 1: Environment Awareness
Understand the environment ladder:
local → staging → production
| Environment | Purpose | Who Sees It | Data |
|---|---|---|---|
| Local | Dev and debugging | Developer only | Mock / seed data |
| Staging | Pre-production validation | Team / QA | Synthetic data mirroring production |
| Production | Real users | Everyone | Real data — handle with care |
Rules
- Code flows one direction: local → staging → production. Never hotfix production directly.
- Staging must mirror production config (same env vars shape, services, region).
- Database migrations run on staging first. Always.
Phase 2: Pre-Deploy Checklist
Before deploying to production, verify ALL items:
- [ ] All pre-merge verification passed (tsc, build, tests)
- [ ] Staging deployment succeeded
- [ ] Staging smoke test passed (critical user journey works)
- [ ] Database migrations tested on staging
- [ ] Environment variables verified (no missing keys)
- [ ] Feature flags configured (if progressive rollout)
- [ ] Rollback plan documented (what to revert and how)
- [ ] Team notified of deploy window
Phase 3: Choose Deployment Strategy
Direct Deploy (Solo / Small Team)
git push origin main → CI builds → auto-deploy → smoke test
When: Solo builders, early-stage, low-traffic apps.
Staged Rollout (Growth / Enterprise)
main → staging deploy → smoke test → canary (5%) → monitor → full rollout
When: Significant user base, changes with behavioral risk.
Blue-Green Deployment (Zero Downtime)
Two identical environments. Switch traffic from old (blue) to new (green). When: Zero-downtime requirement, critical production services.
Phase 4: Database Migration Safety
Migrations are the highest-risk part of deployment:
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.
- 2d ago First seen · 144 lines · 119 tokens per session scan A 31a9e8030a68
pwp-deploy is a skill published in the GitHub repository shandar/pwp-plugin (1 stars, last pushed 6mo ago), licensed MIT. It adds 119 tokens to every session and 1,262 once invoked, about $0.0006 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-31.
Other skills, from other repositories
land-and-deploy
Land and deploy workflow. (gstack).
r2-upload
Upload files to Cloudflare R2, AWS S3, or any S3-compatible storage (like MinIO) and generate secure, time-limited presigned download links with configurable expiration, typically set to 5 minutes. Use when the user needs to upload a file to cloud storage and get a shareable link, or mentions R2, S3, presigned URLs…
aws-solution-architect
../../../engineering-team/skills/aws-solution-architect/SKILL.md.
azure-cloud-architect
../../../engineering-team/skills/azure-cloud-architect/SKILL.md.
release
Release workflow for deploying OpenEnv environments to Hugging Face Spaces and keeping canonical references in sync.
zcf-release
Automate version release and code commit using changeset.