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 humanerd-drew/opencode-drewgent --skill kanban-dispatcher-hardeninggit clone --depth 1 https://github.com/humanerd-drew/opencode-drewgentWrote 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/humanerd-drew/opencode-drewgent/kanban-dispatcher-hardening)<a href="https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/kanban-dispatcher-hardening"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/kanban-dispatcher-hardening/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/humanerd-drew/opencode-drewgent/kanban-dispatcher-hardening"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/kanban-dispatcher-hardening.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.00000 | $0.02816 |
| Opus 5 | $0.00000 | $0.01408 |
| Sonnet 5 | $0.00000 | $0.00563 |
| Haiku 4.5 | $0.00000 | $0.00282 |
Grade A, and why
kanban-dispatcher-hardening scanned grade A with 1 finding 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 11d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
기존 dispatcher는 `subprocess.PIPE`로 worker stdout을 받아 처리하려 했음: How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
2. worker watchdog (Phase 0 — dead worker 즉시 reclaim)
문제
기존 dispatcher는 TTL 만료(claim_expires < now)시에만 in_progress task를 reclaim. 그런데 worker process가 비정상 종료 (segfault, OOM kill, parent kill)되면 claim_expires가 만료될 때까지 1시간 동안 queue stuck.
해결
Phase 0 추가: os.kill(pid, 0)로 worker 생존 확인, dead면 즉시 reclaim.
Board 필터 적용 (cross-board race 차단):
각 dispatcher는 자기 board의 in_progress만 본다. default/content/integrations 3개 dispatcher가 동시에 돌 때, 한 dispatcher가 다른 board의 dead worker를 reclaim해버리는 race를 차단.
# Phase 0: watchdog (board-scoped)
in_progress = conn.execute('''
SELECT id, title, worker_pid FROM tasks
WHERE status = "in_progress" AND worker_pid IS NOT NULL AND board = "self_board"
''').fetchall()
content는 legacy 호환:
WHERE status = "in_progress" AND worker_pid IS NOT NULL AND (board = "content" OR board = "" OR board IS NULL)
Phase 1 (TTL reclaim)도 동일하게 board 필터:
stale = conn.execute('''
SELECT id, title, worker_pid, claim_expires FROM tasks
WHERE status = "in_progress"
AND claim_expires IS NOT NULL
AND claim_expires < ?
AND board = "self_board"
ORDER BY claim_expires ASC
''', (now_ts,)).fetchall()
# Phase 0: watchdog
in_progress = conn.execute('''
SELECT id, title, worker_pid FROM tasks
WHERE status = "in_progress" AND worker_pid IS NOT NULL
''').fetchall()
for task_id, title, wpid in in_progress:
try:
os.kill(int(wpid), 0) # signal 0 = existence check (no actual signal)
except (ProcessLookupError, OSError):
# Worker dead — 즉시 reclaim
conn.execute('UPDATE tasks SET status="ready", worker_pid=NULL, claim_expires=NULL WHERE id=?', (task_id,))
result['watchdog_reclaimed'] += 1
출력 형식
watchdog_reclaimed=N | ttl_reclaimed=M | claimed=K | spawned=L
watchdog_reclaimed: Phase 0가 dead worker로 reclaim한 수ttl_reclaimed: Phase 1가 TTL 만료로 reclaim한 수 (기존)claimed: Phase 2가 ready task를 claim한 수spawned: Phase 3가 worker를 spawn한 수
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.
- 11d ago First seen · 253 lines · 0 tokens per session scan A 0336543285ef
kanban-dispatcher-hardening is a skill published in the GitHub repository humanerd-drew/opencode-drewgent (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,816 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
status
Display current FIRE project status and validate integrity of intents, work items, and runs.