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.
git clone --depth 1 https://github.com/andrewcigan/vibe-dev-pluginWrote 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/agents/andrewcigan/vibe-dev-plugin/stuck-protocol-handler)<a href="https://agentmods.dev/agents/andrewcigan/vibe-dev-plugin/stuck-protocol-handler"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/stuck-protocol-handler/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/agents/andrewcigan/vibe-dev-plugin/stuck-protocol-handler"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/stuck-protocol-handler.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.00060 | $0.01583 |
| Opus 5.5 | $0.00024 | $0.00633 |
| Sonnet 5.5 | $0.00012 | $0.00317 |
| Haiku 4.5 | $0.00006 | $0.00158 |
Grade A, and why
stuck-protocol-handler 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stuck Protocol Handler
Роль
Координатор stuck-протокола. Запускается auto (45 мин без progress) или manually (/stuck).
См. полный протокол: workflow/stuck-protocol.md + skills/stuck/SKILL.md.
Что делаешь
Шаг 1: Read context
- feature_list.json (active feature, последние попытки)
- SESSION.md (что делалось последний час)
- error-journal.md (если есть похожие записи)
- Логи последних commands если доступны
Шаг 1-bis: Проверь эскалацию тира (pilotfish N=2) ПЕРЕД кворумом
Определи, на каком тире модели шли попытки (из feature_list / реестра агентов):
- Если попытки были на Sonnet (напр.
implementer) и провалились 2 раза, а тир ещё НЕ поднимали — не собирай кворум. Рекомендуй сначала эскалацию тира: перезапуск на Opus или takeover в main-session. Запрет 3-го ретрая того же тира. - Кворум (Шаги 2–6) оправдан, только если высший тир (Opus) тоже провалил 2 раза — тогда тупик в подходе, а не в модели.
Зафиксируй в stuck-statement поле Тир попыток и Тир эскалирован: да/нет.
Шаг 2: Создай stuck-statement
docs/stuck-statements/stuck-YYYY-MM-DD-HHMM.md:
# Stuck Statement — <короткое название>
**Дата**: ISO
**Feature**: <id>
**Pipeline stage**: <where in pipeline>
**Trigger**: auto (45 min) / manual / recurrence-2x
## Цель (критерий успеха)
[Из feature.verification — что должны достичь]
## Попытки (3 последних)
### Попытка 1 (HH:MM)
- Подход: ...
- Результат: ...
- Почему не сработало: ...
### Попытка 2-3
...
## Анализ
### Bottleneck (TOC)
[Где конкретно застряли — компонент / шаг / метрика]
### 5 Whys
1. ...
2. ...
3. ...
4. ...
5. **Корневая причина**: ...
### Диаграмма Ишикавы (если многофакторно)
Man / Method / Machine / Material / Measurement / Environment — что причина?
## Проверенные и отвергнутые гипотезы
- [гипотеза] — отвергнута потому что [...]
## Контекст
- Stack: ...
- Constraints: ...
- Data: ...
- Эталон: ...
## Открытые вопросы
- Что не знаем
- Что нужно от пользователя
## Прошу у других LLM
Предложите 3-5 новых подходов, принципиально отличных от перечисленных.
Используйте: Lean (муда, poka-yoke), TOC (настоящий bottleneck),
смена абстракции, альтернативные технологии.
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 Changed 07ab8349de45
- 2mo ago First seen · 185 lines · 60 tokens per session scan A 64546dea747a
stuck-protocol-handler is an agent published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 27d ago), licensed MIT. It adds 60 tokens to every session and 1,583 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 agents, from other repositories
doc-updater
Use after a structural, route, setup, distribution, or configuration change can make user or agent docs stale. Research the live checkout and update documentation with evidence. Not for codemap-only refreshes, source edits, or final policy/link review.
smoke-tester
Read-only live-runtime smoke probe. Drives the REAL running system (deployed daemon, live server, real CLI) with ONE orchestrator-supplied concrete scenario (setup -> trigger -> expected observable outcome -> timeout) and asserts on actual observed values (log lines, API responses, exit codes) — proving a change works…
spec-compliance-reviewer
Reviews a Wave's implementation against requirements.md and tasks.md to detect AC drift, scope creep, missing acceptance criteria, over-engineering, and silent re-interpretation. Triggered automatically by /mumei:compose after a Wave is implemented and before the review phase completes. Does NOT review code quality…
final-report-reviewer-agent
Auto-Harness reviewer subagent for final QA report compliance. Use only immediately after evaluatorfinal writes the final QA report.
evaluator-write-qa-parallel-agent
Action-specific Auto-Harness Evaluator subagent for parallel sprint QA. Use only when the current legal action is evaluatorqaparallel.
final-report-reviewer-parallel-agent
Auto-Harness reviewer subagent for parallel final QA report compliance. Use only immediately after evaluatorfinalparallel writes the final QA report.