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 omnicoreos/planka-mcp --skill planka-orchestratorgit clone --depth 1 https://github.com/omnicoreos/planka-mcpWrote 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/omnicoreos/planka-mcp/planka-orchestrator)<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.
<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>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.00077 | $0.01541 |
| Opus 5 | $0.00039 | $0.00771 |
| Sonnet 5 | $0.00015 | $0.00308 |
| Haiku 4.5 | $0.00008 | $0.00154 |
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.
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
- Read the repository's agent instructions and workflow documentation.
- Check the base tree and current worktrees without changing them.
- 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. - If you are resuming work you did not start, or the session was compacted, call
planka_board_activitybefore 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. - Pull the candidate column with
planka_find_cardsand itslistId: that reads one whole column in a single request, with nothing clipped. - For every candidate card, read the description and ALL comments in order:
planka_get_cardreturns a digest and no comments unless you passwithComments, andplanka_get_commentspages 50 at a time. TrusthasMoreandnextBeforeId, never the count you see in one answer. - Confirm the card has acceptance criteria and one behavior label.
- Resolve
serialandzone:*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.
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.
- 7d ago Changed · +29 lines 736ef33921d3
- 11d ago First seen · 127 lines · 77 tokens per session scan A c604a3084275
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.
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.
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.
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.
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.
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.
vendor-management
Manage ServiceNow vendors and contracts — corecompany vendor records, astcontract with renewal alerts, astcontractsla performance tracking, vendorriskassessment scoring, and vendor scorecards.