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 skills add BostonOrange/claude-code-framework --skill deploygit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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.
[](https://agentmods.dev/skills/bostonorange/claude-code-framework/deploy)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/deploy"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/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.
<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/deploy"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00035 | $0.00424 |
| Opus 5.5 | $0.00014 | $0.00170 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 74 lines · 35 tokens per session scan A de631dfe2faa
deploy is a skill published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 424 once invoked, about $0.0001 per session on Opus 5.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
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…