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/bostonorange/claude-code-framework/deploynpx skills add BostonOrange/claude-code-framework --skill deploygit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWhat 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.00035 | $0.00424 |
| Opus 5 | $0.00017 | $0.00212 |
| Sonnet 5 | $0.00007 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
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 yesterday.
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.
What it actually says
Deploy
Orchestrate deployments to target environments.
Usage
/deploy TICKET-1234 # Deploy a single ticket
/deploy TICKET-1234 TICKET-5678 # Deploy multiple tickets
/deploy --env staging # Deploy to specific environment
Process
Step 1: Identify What to Deploy
For each ticket ID:
- Find the associated PR
- Verify PR is approved and checks pass
- Collect ticket metadata (title, type, manual steps)
Step 2: Pre-Deploy Checks
- All PRs approved
- All CI checks passing
- No merge conflicts
- Manual pre-deploy steps documented (if any)
Step 3: Execute Pre-Deploy Steps
If manual-steps.md has Pre-Deployment section, execute those steps first.
Step 4: Merge PRs
gh pr merge {pr_number} --merge
Step 5: Deploy
{{DEPLOY_COMMAND}}
Step 6: Post-Deploy Steps
If manual-steps.md has Post-Deployment section, execute or prompt for manual steps.
Step 7: Notify
{{NOTIFY_DEPLOY_SUCCESS}}
Step 8: Update Tracker
{{TRACKER_SET_DEPLOYED}}
Edge Cases
| Scenario | Behavior |
|---|---|
| PR not approved | Warn, don't proceed |
| CI checks failing | Warn, don't proceed |
| Merge conflict | Attempt auto-resolve or halt |
| Deploy fails | Post error, rollback if possible |
| Manual steps required | Pause, list steps, wait for confirmation |
Related Skills
/develop— creates the PR that this skill deploys/factory— factory pipeline auto-deploys via CI
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.
- yesterday First seen · 74 lines · 35 tokens per session scan A de631dfe2faa
deploy is a skill published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 424 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…