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-stuck-task-recoverygit 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-stuck-task-recovery)<a href="https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/kanban-stuck-task-recovery"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/kanban-stuck-task-recovery/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-stuck-task-recovery"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/kanban-stuck-task-recovery.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.01141 |
| Opus 5 | $0.00000 | $0.00571 |
| Sonnet 5 | $0.00000 | $0.00228 |
| Haiku 4.5 | $0.00000 | $0.00114 |
Grade A, and why
kanban-stuck-task-recovery 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 9d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: kanban-stuck-task-recovery description: Diagnose and recover stuck kanban in_progress tasks (worker dead, claim_expires expired, dispatcher down). Includes SQL reset script, root cause analysis, and preventive monitoring. type: skill space: outcome tags: [skill, kanban, operations] created: 2026-05-31 updated: 2026-05-31 links:
- "[[@memory/kanban/KANBAN_INDEX]]"
- "[[@memory/growth/kanban-maintenance-guide]]"
- "[[@identity/brain/rules]]"---
Kanban Stuck Task Diagnosis & Recovery
When to Use
task_list(status='in_progress')returns tasks with no worker running- Worker processes (PID) are dead but tasks remain stuck in
in_progress claim_expirestimestamps are past the current time- After a dispatcher outage, tasks need to be reset before the system resumes
Diagnosis
# 1. Find all in_progress tasks with their worker status
python3 -c "
import sqlite3
db = '~/.{{AGENT_NAME_LOWER}}/P2-hippocampus/kanban/state/{{AGENT_NAME_LOWER}}_tasks.db'
conn = sqlite3.connect(db)
cur = conn.cursor()
for id_, title, board, pid, expires in cur.execute(
'SELECT id, title, board, worker_pid, claim_expires FROM tasks WHERE status=\"in_progress\"'
):
print(f'{id_} | board={board} | pid={pid} | expires={expires}')
conn.close()
"
# 2. Check if worker PIDs are alive
ps -p 68898 -o pid,etime 2>/dev/null || echo "worker PID 68898 is DEAD"
Recovery Script
# Reclaim all stale in_progress tasks (expired claim_expires)
python3 -c "
import sqlite3
from datetime import datetime, timezone
db = '~/.{{AGENT_NAME_LOWER}}/P2-hippocampus/kanban/state/{{AGENT_NAME_LOWER}}_tasks.db'
conn = sqlite3.connect(db)
cur = conn.cursor()
stale = cur.execute('''
SELECT id, title, worker_pid, claim_expires
FROM tasks
WHERE status='in_progress'
AND (worker_pid IS NULL OR claim_expires < datetime('now'))
''').fetchall()
print(f'Found {len(stale)} stale in_progress tasks')
reclaimed = 0
for row in stale:
tid = row[0]
cur.execute('''
UPDATE tasks
SET status='ready', worker_pid=NULL, claim_expires=NULL, started_at=NULL
WHERE id=? AND status='in_progress'
''', (tid,))
if cur.rowcount > 0:
print(f'RECLAIMED: {tid}')
reclaimed += 1
conn.commit()
print(f'Total reclaimed: {reclaimed}')
conn.close()
"
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.
- 9d ago First seen · 131 lines · 0 tokens per session scan A 9b0cc4a3857f
kanban-stuck-task-recovery 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 1,141 tokens. 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.