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/furkangonel/cowrangler/github-pr-workflownpx skills add furkangonel/cowrangler --skill github-pr-workflowgit clone --depth 1 https://github.com/furkangonel/cowranglerWhat 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.00025 | $0.01519 |
| Opus 5 | $0.00013 | $0.00759 |
| Sonnet 5 | $0.00005 | $0.00304 |
| Haiku 4.5 | $0.00003 | $0.00152 |
Grade B, and why
github-pr-workflow scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
| PR kapat | `gh pr close N` | `curl -X PATCH .../pulls/N -d '{"state":"closed"}'` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
PR yaşam döngüsünü yönetmek için kapsamlı rehber. Her bölüm önce `gh` CLI yolunu, ardından `git` + `curl` geri dönüş yolunu gösterir. How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Pull Request İş Akışı
PR yaşam döngüsünü yönetmek için kapsamlı rehber. Her bölüm önce gh CLI yolunu, ardından git + curl geri dönüş yolunu gösterir.
Ön Koşullar
- GitHub'a kimlik doğrulama yapılmış (
gh auth loginveyaGITHUB_TOKENenv değişkeni) - GitHub remote'u olan bir git deposunun içinde
Auth Algılama
if command -v gh &>/dev/null && gh auth status &>/dev/null; then
AUTH="gh"
else
AUTH="git"
if [ -z "$GITHUB_TOKEN" ]; then
GITHUB_TOKEN=$(grep "^GITHUB_TOKEN=" ~/.cowrangler/credentials.env 2>/dev/null | head -1 | cut -d= -f2 | tr -d '\n\r')
fi
fi
REMOTE_URL=$(git remote get-url origin)
OWNER_REPO=$(echo "$REMOTE_URL" | sed -E 's|.*github\.com[:/]||; s|\.git$||')
OWNER=$(echo "$OWNER_REPO" | cut -d/ -f1)
REPO=$(echo "$OWNER_REPO" | cut -d/ -f2)
1. Branch Oluştur
git fetch origin
git checkout main && git pull origin main
git checkout -b feat/kullanici-girisi-ekle
Branch isimlendirme:
feat/açıklama— yeni özelliklerfix/açıklama— hata düzeltmelerirefactor/açıklama— yeniden yapılandırmadocs/açıklama— belgelerci/açıklama— CI/CD değişiklikleri
2. Commit
git add src/auth.ts tests/auth.test.ts
git commit -m "feat: JWT tabanlı kullanıcı kimlik doğrulaması ekle
- Giriş/kayıt endpoint'leri eklendi
- Şifre hashleme ile User modeli eklendi
- Korumalı route'lar için auth middleware eklendi"
Conventional Commits formatı:
type(scope): kısa açıklama
Gerekirse uzun açıklama. 72 karakterde sar.
Tipler: feat, fix, refactor, docs, test, ci, chore, perf
3. Push ve PR Oluştur
git push -u origin HEAD
gh ile:
gh pr create \
--title "feat: JWT tabanlı kullanıcı kimlik doğrulaması" \
--body "## Özet
- Giriş/kayıt API endpoint'leri
- JWT token üretimi ve doğrulaması
## Test Planı
- [ ] Birim testleri geçiyor
Closes #42"
curl ile:
BRANCH=$(git branch --show-current)
curl -s -X POST \
-H "Authorization: token $GITHUB_TOKEN" \
-H "Accept: application/vnd.github.v3+json" \
https://api.github.com/repos/$OWNER/$REPO/pulls \
-d "{\"title\":\"feat: JWT kimlik doğrulaması\",\"body\":\"Closes #42\",\"head\":\"$BRANCH\",\"base\":\"main\"}"
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 · 178 lines · 25 tokens per session scan B aec43fd01275
github-pr-workflow is a skill published in the GitHub repository furkangonel/cowrangler (2 stars, last pushed 4d ago), licensed MIT. It adds 25 tokens to every session and 1,519 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
deck-obsidian-claude
GitHub-dark + 紫蓝环境光 + 三色渐变标题 + GitHub 风代码.
humanize
This skill should be used when writing or revising text, including responses, documentation, comments, emails, posts, reports, and messages, especially when the user asks to "humanize", "write naturally", "remove AI tone", or "avoid AI writing".
create-pr
This skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or explicitly invokes "create-pr".
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
gcloud-usage
This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".