Borrowing it
Nothing to install: this file belongs to yylo-dev/yylo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yylo-dev/yylo/main/.agents/skills/plan-kanban-tasks/SKILL.mdgit clone --depth 1 https://github.com/yylo-dev/yyloWrote 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/yylo-dev/yylo/plan-kanban-tasks)<a href="https://agentmods.dev/skills/yylo-dev/yylo/plan-kanban-tasks"><img src="https://agentmods.dev/badge/skills/yylo-dev/yylo/plan-kanban-tasks/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/yylo-dev/yylo/plan-kanban-tasks"><img src="https://agentmods.dev/badge/skills/yylo-dev/yylo/plan-kanban-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00294 |
| Opus 5.5 | $0.00013 | $0.00118 |
| Sonnet 5.5 | $0.00006 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
plan-kanban-tasks 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 1mo 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.
What it actually says
Plan Kanban work
- Read the project instructions and relevant product code from the integration or feature worktree. Read existing task/spec metadata through the canonical controller; do not assume
.juno_task/plan.mdexists. - Produce one concise PDR covering the goal, current behavior, scope, exclusions, risks, dependencies, acceptance criteria, and focused tests.
- Split only when pieces can be implemented and validated independently. Concurrent tasks must have explicit path ownership and dependencies.
- Create tasks through the controller's
.juno_task/scripts/kanban.sh. Put durable requirements and acceptance criteria in each task body; relate follow-ups instead of reopening archived IDs. - Store any durable specification through a controller-authorized metadata operation. Never create controller-private
.juno_task/specs, tasks, ledger, state, or receipts inside a product or feature worktree. - Do not start implementation, create worktrees, push, deploy, or mutate production unless the user separately asks.
Use --id, not legacy --ID, for Kanban mutations. Return the task IDs and a short dependency/order summary.
$ARGUMENTS
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.
- 1mo ago First seen · 20 lines · 32 tokens per session scan A b5c661a74724
plan-kanban-tasks is a skill published in the GitHub repository yylo-dev/yylo (66 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 294 once invoked, about $0.0001 per session on Opus 5.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
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip-board
Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.
summarize-status
Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.
first-task
Guide the user's first Paperclip task when its description invokes /first-task. Interpret the opening answer, clarify their goal, propose a plan or a single task, and wait for approval before hiring agents or executing approved work.
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).