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-close-cardgit 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-close-card)<a href="https://agentmods.dev/skills/omnicoreos/planka-mcp/planka-close-card"><img src="https://agentmods.dev/badge/skills/omnicoreos/planka-mcp/planka-close-card/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-close-card"><img src="https://agentmods.dev/badge/skills/omnicoreos/planka-mcp/planka-close-card.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.00815 |
| Opus 5 | $0.00037 | $0.00407 |
| Sonnet 5 | $0.00015 | $0.00163 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
planka-close-card 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close a Planka workflow card
Closure is evidence plus a truthful state transition. Do not move a card merely because implementation stopped.
Read first
- Read the card description and every comment:
planka_get_cardwithwithComments, orplanka_get_comments.get_cardis a digest and returns no comments unless asked, and comments page 50 at a time — keep paging whilehasMoreis true instead of trusting one answer. The description says how the card was born; the comments say where it stands today, and the last one wins. - If you are picking up a card someone else worked on, run
planka_board_activityorplanka_card_historyfirst: they say what moved and who moved it. - Read the repository's contribution and verification instructions.
- Resolve the
<!-- agent-work -->branch and worktree against real Git state. - Determine your role:
- worker: edits, verifies, commits, and writes the handoff;
- director: audits, merges, cleans, and changes board state;
- human confirmation handler: records
tested-okand completes the final move.
Do not perform another role's transition unless the user explicitly assigned both roles and the repository allows it.
Every board write you make (planka_create_comment, planka_move_card,
planka_set_card_labels, planka_update_card) re-reads what it touched and reports
verified. Read that field before claiming the card moved or the comment landed: a
response without it confirmed nothing.
Worker closure
The worker must:
- Run the relevant repository checks.
- Execute the card's observable acceptance step.
- Capture visual evidence when the change is visual.
- Record any skipped or impossible proof explicitly.
- Commit all intended files and confirm the worktree is clean.
- Leave this comment on the assigned card:
✅ Ready for review
**Changed:** <one user-visible sentence>
**Where to check:** <URL, command, or exact path>
**Prove it:** <one concrete acceptance step>
**Risk:** <real nearby behavior that could regress>
**Verified:** <checks and manual evidence, with honest omissions>
**Commit:** <commit SHA>
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 · +13 lines a6d706afc432
- 11d ago First seen · 82 lines · 74 tokens per session scan A c089b5843349
planka-close-card is a skill published in the GitHub repository omnicoreos/planka-mcp (2 stars, last pushed 8d ago), licensed MIT. It adds 74 tokens to every session and 815 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.
sla-management
Configure ServiceNow SLAs — contractsla definitions with start/stop/pause/cancel conditions, tasksla status checks, breach escalation, business-hours schedules, and compliance-rate aggregation.