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/push/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/push)<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/push"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/push/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/push"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/push.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.00054 | $0.02065 |
| Opus 5.5 | $0.00022 | $0.00826 |
| Sonnet 5.5 | $0.00011 | $0.00413 |
| Haiku 4.5 | $0.00005 | $0.00206 |
Grade A, and why
push 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/push - Safe Push Pipeline
$ARGUMENTS
Purpose
All-in-one command that validates code quality, ensures test coverage, generates a meaningful commit message, and pushes to remote. Prevents broken code, leaked secrets, and lazy commits from reaching the repository.
Sub-commands
/push - Full pipeline: check → stage → commit → push
/push check - Run all checks without committing or pushing
/push --force - Skip checks (shows warning, requires confirmation)
/push --amend - Amend last commit and force-push (shows warning)
Behavior
When /push is triggered:
Phase 1: Pre-Push Checks
Run these checks sequentially. Stop on any Critical failure.
1.1 Branch Safety
Run: git branch --show-current
| Condition | Action |
|---|---|
Branch is main or master |
WARN: "Direkt main'e push ediyorsun. Emin misin?" — Kullanıcı onayı gerekli |
| Branch is behind remote | WARN: "Remote'da yeni commit'ler var. Önce git pull önerilir" |
| Branch is up to date | OK |
1.2 Secret Scan
Search staged files for:
- API keys: /[A-Za-z0-9_]{20,}/ in suspicious contexts
- Passwords: password\s*=\s*["'][^"']+
- Tokens: token\s*=\s*["'][^"']+
- AWS keys: AKIA[0-9A-Z]{16}
- Private keys: -----BEGIN.*PRIVATE KEY-----
- .env files staged
| Finding | Action |
|---|---|
| Secret detected | CRITICAL STOP — Do NOT proceed. Show file:line and ask user to remove |
.env file staged |
CRITICAL STOP — ".env dosyası commit'e dahil. Kaldır." |
| Clean | OK |
1.3 Debug Statement Scan
Search staged files for:
- console.log (JS/TS)
- print() without context (Python)
- debugger (JS/TS)
- binding.pry (Ruby)
- dd() (PHP)
| Finding | Action |
|---|---|
| Debug statements found | WARN — List them, ask: "Bunlar kalmalı mı?" |
| Clean | OK |
1.4 Lint Check
Detect and run project linter:
- package.json has "lint" script → npm run lint
- .eslintrc exists → npx eslint .
- ruff.toml/.flake8 exists → ruff check . / flake8
- No linter → Skip with note
| Result | Action |
|---|---|
| Lint errors | WARN — Show errors, ask: "Düzelteyim mi?" |
| Lint clean | OK |
| No linter configured | SKIP — Note in report |
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 · 294 lines · 54 tokens per session scan A e5d2e3a1155c
push is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 6mo ago), licensed MIT. It adds 54 tokens to every session and 2,065 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…