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 SaikaAco/saika-hermes-skills --skill kanban-workflowsgit clone --depth 1 https://github.com/SaikaAco/saika-hermes-skillsWrote 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/saikaaco/saika-hermes-skills/kanban-workflows)<a href="https://agentmods.dev/skills/saikaaco/saika-hermes-skills/kanban-workflows"><img src="https://agentmods.dev/badge/skills/saikaaco/saika-hermes-skills/kanban-workflows/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/saikaaco/saika-hermes-skills/kanban-workflows"><img src="https://agentmods.dev/badge/skills/saikaaco/saika-hermes-skills/kanban-workflows.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.00039 | $0.01322 |
| Opus 5 | $0.00019 | $0.00661 |
| Sonnet 5 | $0.00008 | $0.00264 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
kanban-workflows 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 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.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kanban Workflows
Overview
Use this umbrella for Hermes Kanban work regardless of whether the current agent is acting as the orchestrator or as a worker. The old orchestrator/worker split encoded two roles of the same class-level workflow; keeping them together makes it easier to load the right lifecycle and avoid role confusion.
When to Use
- The user asks to coordinate a multi-step effort through Kanban.
- You are operating under a Kanban orchestrator profile.
- You are a worker assigned a Kanban ticket and need lifecycle/pitfall guidance.
- Work requires decomposition, ticket updates, acceptance criteria, or handoff notes.
Don't use this for a normal one-agent todo list; use the session todo tool unless a real Kanban board/workflow is in scope.
Route before creating work
| Work shape | Use |
|---|---|
| Short deterministic work in the current turn | Direct tools or execute_code |
| Short bounded reasoning that can fork and rejoin the live parent | delegate_task |
| Work that must survive restart, carry dependencies, retry, wait for human review, or run across profiles | Kanban |
Do not use delegate_task for work whose result must outlive the parent
process. Do not use Kanban for a quick lookup or one-agent session todo.
Retry-safe task creation
- Discover real profile names before assignment; never invent an assignee.
- Supply a stable
idempotency_keyfor any task creation that may be retried. Reuse the same key after transport uncertainty so the kernel returns the existing non-archived task instead of creating a duplicate. - Set
max_runtime_secondsfor bounded workers. - Agent tool-created tasks use configured
kanban.failure_limit; operators using the CLI/API may additionally set per-taskmax_retries. After repeated failure, block for review or reassign; never respawn the same unchanged task indefinitely. - Create parent cards first and pass
parents=[...]when creating children. Do not create children as ready and link them afterward.
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 · 128 lines · 39 tokens per session scan A 7cd652a95c84
kanban-workflows is a skill published in the GitHub repository SaikaAco/saika-hermes-skills (2 stars, last pushed 13d ago), licensed MIT. It adds 39 tokens to every session and 1,322 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
gh-issues
Triage GitHub issues, select safe candidates, implement focused fixes, open pull requests, and address actionable review feedback.
document-to-action-items
Turn documents, notes, transcripts, and meeting records into traceable action items, decisions, owners, deadlines, and follow-ups without inventing missing commitments.
github
Use GitHub CLI for repositories, issues, pull requests, reviews, CI runs, releases, and structured GitHub API queries.
kill-the-standup
Reads yesterday's Linear issues and GitHub commits for the authenticated user, formats a standup update (done / doing / blockers), and posts it to Slack. Use when asked to write a standup, generate a standup update, post to the standup channel, summarize yesterday's work, or automate the daily standup. Trigger when a…
hermes-kanbanize
Use when an existing conversation, plan, specification, or objective must become a Hermes-native Kanban board with verifiable work slices, real blocking edges, a clear execution frontier, and no duplicate scheduler.
what-have-we-done-today
Use when a recap of today's sessions, cron, and kanban helps.