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 forcewake/hermes-conductor --skill kanban-orchestratorgit clone --depth 1 https://github.com/forcewake/hermes-conductorWrote 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/forcewake/hermes-conductor/kanban-orchestrator)<a href="https://agentmods.dev/skills/forcewake/hermes-conductor/kanban-orchestrator"><img src="https://agentmods.dev/badge/skills/forcewake/hermes-conductor/kanban-orchestrator/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/forcewake/hermes-conductor/kanban-orchestrator"><img src="https://agentmods.dev/badge/skills/forcewake/hermes-conductor/kanban-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Rogue Agent · line 49 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00021 | $0.03259 |
| Opus 5 | $0.00010 | $0.01630 |
| Sonnet 5 | $0.00004 | $0.00652 |
| Haiku 4.5 | $0.00002 | $0.00326 |
Grade A, and why
kanban-orchestrator 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- kanban-orchestrator — 88% identical, 58 lines differ
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kanban Orchestrator — Decomposition Playbook
The core worker lifecycle (including the
kanban_createfan-out pattern and the "decompose, don't execute" rule) is auto-injected into every kanban process via theKANBAN_GUIDANCEsystem-prompt block. This skill is the deeper playbook when you're an orchestrator profile whose whole job is routing.
Profiles are user-configured — not a fixed roster
Hermes setups vary widely. Some users run a single profile that does everything; some run a small fleet (docker-worker, cron-worker); some run a curated specialist team they've named themselves. There is no default specialist roster — the orchestrator skill does not know what profiles exist on this machine.
Before fanning out, you must ground the decomposition in the profiles that actually exist. The dispatcher silently fails to spawn unknown assignee names — it doesn't autocorrect, doesn't suggest, doesn't fall back. So a card assigned to researcher on a setup that only has docker-worker just sits in ready forever.
Step 0: discover available profiles before planning.
Use one of these:
hermes profile list— prints the table of profiles configured on this machine. Run it through your terminal tool if you have one; otherwise ask the user.kanban_list(assignee="<some-name>")— sanity-check a single name. Returns an empty list (rather than an error) for an unknown assignee, so this only confirms a name you're already considering.- Just ask the user. "What profiles do you have set up?" is a fine first turn when the goal needs more than one specialist.
Cache the result in your working memory for the rest of the conversation. Re-asking every turn wastes a tool call.
When to use the board (vs. just doing the work)
Create Kanban tasks when any of these are true:
- Multiple specialists are needed. Research + analysis + writing is three profiles.
- The work should survive a crash or restart. Long-running, recurring, or important.
- The user might want to interject. Human-in-the-loop at any step.
- Multiple subtasks can run in parallel. Fan-out for speed.
- Review / iteration is expected. A reviewer profile loops on drafter output.
- The audit trail matters. Board rows persist in SQLite forever.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 192 lines · 0 tokens per session scan A c7a0f955d733
kanban-orchestrator is a skill published in the GitHub repository forcewake/hermes-conductor (71 stars, last pushed 14d ago), licensed MIT. It adds 21 tokens to every session and 3,259 once invoked, about $0.0001 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-30.
Other skills, from other repositories
simply-pm
Use when you are spawned as the PM of a simply harness project and your brief references a .simply/LEDGER.md work ledger or this skill. Grants fleet authority, routing doctrine, safe worker lifecycle, and the signal protocol back to the auditor.
agency-chief-of-staff
A coordinator for complex, multi-stage projects that span conversations and tasks. It helps discuss requirements, create execution plans, assign roles, track progress, and preserve useful project knowledge.
dynamic-workflows
Use the hermes-dynamic-workflows plugin: workflow runs, script harnesses, controls, child agents, and Kanban waits.
agency-discuss-plan-execute-progress-archive
Discovery bridge for staged projects: discuss, plan, launch tasks, track progress, verify and archive. Excludes small tasks and source maintenance.
fizzy
Operate a self-hosted Fizzy kanban board via fizzy-cli. Use when setting up fizzy-cli, creating or updating Fizzy cards and comments, or migrating Jira issues to Fizzy.
team-dispatch
Turns a plan phase into a PhaseSpec v1 and dispatches it to a specialist subagent via the Agent tool. Subagent reads files itself, returns a structured result, the result is logged into progress.md. Markdown is the shared state; no in-memory shared store across agents.