planka-orchestrator

planka-orchestrator is a skill for Claude Code from omnicoreos/planka-mcp. It costs 77 tokens per session (1,541 once invoked), scanned A, original, MIT.

A workflow coordinator for managing software tasks represented as cards on a Planka board. It assigns workers to cards, tracks their evidence and branches, and coordinates safe merges.

In plain words
What is it for?
Use it when directing Planka board work, running cards in parallel, dispatching workers, reviewing their changes, or continuing an existing board workflow.
Why use it?
It organizes parallel development work while keeping each task isolated and checking the results before merging.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the planka plugin — 2 skills, 1 hook, 1 MCP server shipped together

Good fit Use it when directing Planka board work, running cards in parallel, dispatching workers, reviewing their changes, or continuing an existing board workflow.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/omnicoreos/planka-mcp/planka-orchestrator
Install

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.

Any agent
npx skills add omnicoreos/planka-mcp --skill planka-orchestrator
Clone the repo
git clone --depth 1 https://github.com/omnicoreos/planka-mcp

Made for: Claude Code.

Or install planka, the plugin that ships this one along with the rest of its 2 skills, 1 hook, 1 MCP server.

Wrote 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.

agentmods badge for planka-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/skills/omnicoreos/planka-mcp/planka-orchestrator/github.svg)](https://agentmods.dev/skills/omnicoreos/planka-mcp/planka-orchestrator)
Your own site
<a href="https://agentmods.dev/skills/omnicoreos/planka-mcp/planka-orchestrator"><img src="https://agentmods.dev/badge/skills/omnicoreos/planka-mcp/planka-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.

agentmods 80×15 button for planka-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/skills/omnicoreos/planka-mcp/planka-orchestrator"><img src="https://agentmods.dev/badge/skills/omnicoreos/planka-mcp/planka-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,541 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.01541
Opus 5 $0.00039 $0.00771
Sonnet 5 $0.00015 $0.00308
Haiku 4.5 $0.00008 $0.00154

Measured 7d ago against content hash 736ef33921d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

planka-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 7d 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.

workflow/skills/planka-orchestrator/SKILL.md · 156 lines

How it starts

The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Planka workflow orchestrator

Use this skill only for the optional workflow documented in workflow/README.md. The Planka MCP server must be connected and the repository must define its own build, test, review, and merge rules.

Role boundary

You are the director. Do not edit repository files. Workers are the only writers: one worker, one card, one branch, one worktree.

The director may:

  • read the repository and board;
  • create and update cards;
  • create worktrees with the repository's supported helper;
  • dispatch or continue workers;
  • audit diffs, commits, checks, comments, and attachments;
  • merge through the repository's supported path;
  • clean completed worktrees.

Preflight

  1. Read the repository's agent instructions and workflow documentation.
  2. Check the base tree and current worktrees without changing them.
  3. Open the board with planka_board_summary: one call returns every column with its card count and every label with its ID. It is the only opening read.
  4. If you are resuming work you did not start, or the session was compacted, call planka_board_activity before anything else: it says what moved, and who moved it, since a given date. Planka logs card creation, moves, member changes and task completion only — comments and edits leave no trace there, so activity narrows where to look, it does not replace reading the cards.
  5. Pull the candidate column with planka_find_cards and its listId: that reads one whole column in a single request, with nothing clipped.
  6. For every candidate card, read the description and ALL comments in order: planka_get_card returns a digest and no comments unless you pass withComments, and planka_get_comments pages 50 at a time. Trust hasMore and nextBeforeId, never the count you see in one answer.
  7. Confirm the card has acceptance criteria and one behavior label.
  8. Resolve serial and zone:* exclusions before creating anything.

Never trust a suspicious zero-comment result blindly. If the card's state implies a decision or prior work, re-read with planka_get_comments and report an MCP/API mismatch.

Read the full file on GitHub · 156 lines

Changes

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.

  1. 7d ago Changed · +29 lines 736ef33921d3
  2. 11d ago First seen · 127 lines · 77 tokens per session scan A c604a3084275

Subscribe to this mod's changes

planka-orchestrator is a skill published in the GitHub repository omnicoreos/planka-mcp (2 stars, last pushed 7d ago), licensed MIT. It adds 77 tokens to every session and 1,541 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-08-31.

Related

Other skills, from other repositories

workspace-builder

Build ServiceNow App Engine Studio applications — sysscope creation, scoped tables, sysawworkspace with lists/forms, the sysux record chain behind UI Builder workspaces, data brokers, and application export readiness checks. Never create a UI Builder page by inserting a sysuxpage row.

serac-labs/serac · 62 tokens

problem-management

Manage ServiceNow problems — create from linked incidents, proactive pattern detection, RCA with 5-Whys, knownerror workarounds (KEDB), KEDB search by CI/category/keywords, and permanent-fix linkage to changes.

serac-labs/serac · 53 tokens

change-management

Create and transition ServiceNow change requests (normal/standard/emergency), change tasks, affected CIs, approval routing, CAB scheduling, and conflict detection across maintenance windows.

serac-labs/serac · 37 tokens

hr-service-delivery

Build ServiceNow HR Service Delivery — snhrcorecase from Employee Center or HR catalog, snhrlelifecycleevent onboarding/offboarding with templated activities, and HR document generation.

serac-labs/serac · 42 tokens

incident-management

Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.

serac-labs/serac · 42 tokens

vendor-management

Manage ServiceNow vendors and contracts — corecompany vendor records, astcontract with renewal alerts, astcontractsla performance tracking, vendorriskassessment scoring, and vendor scorecards.

serac-labs/serac · 40 tokens