Borrowing it
Nothing to install: this file belongs to bugrabilge/bilge-development-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bugrabilge/bilge-development-kit/main/.claude/skills/deploy/SKILL.mdgit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWrote 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/bugrabilge/bilge-development-kit/deploy)<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/deploy"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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/bugrabilge/bilge-development-kit/deploy"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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.00038 | $0.00885 |
| Opus 5.5 | $0.00015 | $0.00354 |
| Sonnet 5.5 | $0.00008 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00089 |
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 2mo 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy - Production Deployment
$ARGUMENTS
Purpose
This command handles production deployment with pre-flight checks, deployment execution, and verification.
Sub-commands
/deploy - Interactive deployment wizard
/deploy check - Run pre-deployment checks only
/deploy preview - Deploy to preview/staging
/deploy production - Deploy to production
/deploy rollback - Rollback to previous version
Pre-Deployment Checklist
Before any deployment:
## 🚀 Pre-Deploy Checklist
### Code Quality
- [ ] No TypeScript errors (`npx tsc --noEmit`)
- [ ] ESLint passing (`npx eslint .`)
- [ ] All tests passing (`npm test`)
### Security
- [ ] No hardcoded secrets
- [ ] Environment variables documented
- [ ] Dependencies audited (`npm audit`)
### Performance
- [ ] Bundle size acceptable
- [ ] No console.log statements
- [ ] Images optimized
### Documentation
- [ ] README updated
- [ ] CHANGELOG updated
- [ ] API docs current
### Ready to deploy? (y/n)
Deployment Flow
┌─────────────────┐
│ /deploy │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Pre-flight │
│ checks │
└────────┬────────┘
│
Pass? ──No──► Fix issues
│
Yes
│
▼
┌─────────────────┐
│ Build │
│ application │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Deploy to │
│ platform │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Health check │
│ & verify │
└────────┬────────┘
│
▼
┌─────────────────┐
│ ✅ Complete │
└─────────────────┘
Output Format
Successful Deploy
## 🚀 Deployment Complete
### Summary
- **Version:** v1.2.3
- **Environment:** production
- **Duration:** 47 seconds
- **Platform:** Vercel
### URLs
- 🌐 Production: https://app.example.com
- 📊 Dashboard: https://vercel.com/project
### What Changed
- Added user profile feature
- Fixed login bug
- Updated dependencies
### Health Check
✅ API responding (200 OK)
✅ Database connected
✅ All services healthy
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.
- 2mo ago First seen · 184 lines · 38 tokens per session scan A 831e8f0237f5
deploy is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 885 once invoked, about $0.0002 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…