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 vibeeval/vibecosystem --skill autonomous-prgit clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/autonomous-pr)<a href="https://agentmods.dev/skills/vibeeval/vibecosystem/autonomous-pr"><img src="https://agentmods.dev/badge/skills/vibeeval/vibecosystem/autonomous-pr/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/vibeeval/vibecosystem/autonomous-pr"><img src="https://agentmods.dev/badge/skills/vibeeval/vibecosystem/autonomous-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Excessive Agency · line 30 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- high Excessive Agency · line 48 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- high Excessive Agency · line 166 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- high Excessive Agency · line 128 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- high Tool Misuse · line 220 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00059 | $0.01860 |
| Opus 5.5 | $0.00024 | $0.00744 |
| Sonnet 5.5 | $0.00012 | $0.00372 |
| Haiku 4.5 | $0.00006 | $0.00186 |
Grade A, and why
autonomous-pr 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.
How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous PR Lifecycle
PR'i olusturmaktan merge'e kadar tum sureci otonom yonet. CI basarisiz olursa duzelt, review feedback gelirse uygula, butce asarsa dur.
PR Pipeline
1. BRANCH → Feature branch olustur
2. IMPLEMENT → Kodu yaz (kraken/spark)
3. VERIFY → Lokal test + lint + build
4. PR CREATE → gh pr create
5. CI WAIT → CI pipeline'i bekle
6. CI FIX → Basarisizsa duzelt, tekrar push (max 3)
7. REVIEW → Review feedback bekle
8. APPLY → Feedback'i uygula
9. READY → Merge'e hazir bildir
Kullanim
Basit: Tek PR
# Claude'a otonom PR olusturttir
claude -p "
Feature: kullanici profil sayfasi ekle
Branch: feat/user-profile
PR target: main
Pipeline:
1. Branch olustur
2. Implement et
3. Test yaz
4. PR olustur
5. CI bekle ve fix et
6. Hazir olunca bildir
"
Gelismis: Budget ve Zaman Limiti
claude -p "
Feature: auth middleware refactor
Branch: refactor/auth-middleware
PR target: main
Limitler:
--budget 500K tokens # Max token harcama
--max-duration 30m # Max sure
--max-ci-retries 3 # Max CI fix denemesi
--auto-merge false # Merge'i ben onaylayacagim
Basarisiz olursa:
Draft PR olarak birak, ne yaptigini acikla
"
CI Fix Dongusu
CI BASARISIZ
│
├─ Build hatasi?
│ └─ build-error-resolver agent cagir
│ └─ Fix → Push → CI tekrar bekle
│
├─ Test basarisiz?
│ └─ Hata mesajini oku
│ ├─ Test kodu hatali → Test'i duzelt
│ └─ Implementation hatali → Kodu duzelt
│ └─ Push → CI tekrar bekle
│
├─ Lint hatasi?
│ └─ Otomatik fix (prettier, eslint --fix)
│ └─ Push → CI tekrar bekle
│
├─ Type hatasi?
│ └─ Type fix uygula
│ └─ Push → CI tekrar bekle
│
└─ 3. deneme basarisiz?
└─ DURR → Draft PR olarak birak
└─ PR body'ye aciklama yaz
CI Fix Script
#!/bin/bash
# scripts/ci-fix-loop.sh
MAX_RETRIES=3
RETRY=0
while [ $RETRY -lt $MAX_RETRIES ]; do
echo "=== CI Check (attempt $((RETRY + 1))/$MAX_RETRIES) ==="
# CI durumunu kontrol et
STATUS=$(gh pr checks --json state -q '.[].state' | sort -u)
if echo "$STATUS" | grep -q "SUCCESS"; then
echo "CI PASSED"
exit 0
fi
if echo "$STATUS" | grep -q "PENDING"; then
echo "CI bekliyor..."
sleep 30
continue
fi
# Basarisiz -- fix dene
RETRY=$((RETRY + 1))
echo "CI FAILED (attempt $RETRY)"
# Hata detayini al
FAILED=$(gh pr checks --json name,state -q '.[] | select(.state=="FAILURE") | .name')
for check in $FAILED; do
echo "Fixing: $check"
# Claude'a fix ettir
claude -p "CI check '$check' failed. Read the error, fix it, commit." --no-input
done
git push
sleep 60 # CI'in yeniden baslamasini bekle
done
echo "CI FIX BASARISIZ ($MAX_RETRIES deneme)"
exit 1
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 · 237 lines · 59 tokens per session scan A 07fb32d32e6a
autonomous-pr is a skill published in the GitHub repository vibeeval/vibecosystem (538 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 1,860 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-09-03.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
turborepo-caching
Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.
bitbucket-workflow
Bitbucket best practices for pull requests, Pipelines CI/CD, Jira integration, and Atlassian ecosystem workflows.
gitlab-workflow
GitLab best practices for merge requests, CI/CD pipelines, issue tracking, and DevOps workflows.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.