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 nativ3ai/hermes-agent-camel --skill kanban-orchestratorgit clone --depth 1 https://github.com/nativ3ai/hermes-agent-camelWrote 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/nativ3ai/hermes-agent-camel/kanban-orchestrator)<a href="https://agentmods.dev/skills/nativ3ai/hermes-agent-camel/kanban-orchestrator"><img src="https://agentmods.dev/badge/skills/nativ3ai/hermes-agent-camel/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/nativ3ai/hermes-agent-camel/kanban-orchestrator"><img src="https://agentmods.dev/badge/skills/nativ3ai/hermes-agent-camel/kanban-orchestrator.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.00074 | $0.01904 |
| Opus 5 | $0.00037 | $0.00952 |
| Sonnet 5 | $0.00015 | $0.00381 |
| Haiku 4.5 | $0.00007 | $0.00190 |
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 8d 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
3 near-identical copies found in the catalogue:
- kanban-orchestrator — 100% identical, 0 lines differ
- kanban-orchestrator — 92% identical, 10 lines differ
- kanban-orchestrator — 89% identical, 15 lines differ
How it starts
The opening of the file, as written. The whole thing — 153 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.
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.
If none of those apply — it's a small one-shot reasoning task — use delegate_task instead or answer the user directly.
The anti-temptation rules
Your job description says "route, don't execute." The rules that enforce that:
- Do not execute the work yourself. Your restricted toolset usually doesn't even include terminal/file/code/web for implementation. If you find yourself "just fixing this quickly" — stop and create a task for the right specialist.
- For any concrete task, create a Kanban task and assign it. Every single time.
- If no specialist fits, ask the user which profile to create. Do not default to doing it yourself under "close enough."
- Decompose, route, and summarize — that's the whole job.
The standard specialist roster (convention)
Unless the user's setup has customized profiles, assume these exist. Adjust to whatever the user actually has — ask if you're unsure.
| Profile | Does | Typical workspace |
|---|---|---|
researcher |
Reads sources, gathers facts, writes findings | scratch |
analyst |
Synthesizes, ranks, de-dupes. Consumes multiple researcher outputs |
scratch |
writer |
Drafts prose in the user's voice | scratch or dir: into their Obsidian vault |
reviewer |
Reads output, leaves findings, gates approval | scratch |
backend-eng |
Writes server-side code | worktree |
frontend-eng |
Writes client-side code | worktree |
ops |
Runs scripts, manages services, handles deployments | dir: into ops scripts repo |
pm |
Writes specs, acceptance criteria | scratch |
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.
- 8d ago First seen · 153 lines · 74 tokens per session scan A 7d2c9c4296d3
kanban-orchestrator is a skill published in the GitHub repository nativ3ai/hermes-agent-camel (196 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 1,904 once invoked, about $0.0004 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-09-03.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.