yylo: Skill for Claude Code

.agents/skills/plan-kanban-tasks/SKILL.md

plan-kanban-tasks is a skill for Claude Code, Codex from yylo-dev/yylo. It costs 32 tokens per session (294 once invoked), scanned A, original, MIT.

A planning skill that turns a requested product change into a concise requirement and one or more implementation-sized kanban tasks.

In plain words
What is it for?
Use it when the user explicitly asks to plan work or register it on the task board.
Why use it?
It breaks broad requests into work items that are easier to understand, assign, and complete.

Skill for Claude CodeCodex

Written for Claude Code: argument-hint in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is yylo-dev/yylo's own configuration. It tells Claude Code and Codex how to work on yylo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything yylo configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/yylo-dev/yylo/main/.agents/skills/plan-kanban-tasks/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/yylo-dev/yylo

Made for: Claude Code, Codex.

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 plan-kanban-tasks

README.md
[![agentmods](https://agentmods.dev/badge/skills/yylo-dev/yylo/plan-kanban-tasks/github.svg)](https://agentmods.dev/skills/yylo-dev/yylo/plan-kanban-tasks)
Your own site
<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.

agentmods 80×15 button for plan-kanban-tasks

Your own site · 80×15
<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>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 294 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00032 $0.00294
Opus 5 $0.00016 $0.00147
Sonnet 5 $0.00006 $0.00059
Haiku 4.5 $0.00003 $0.00029

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

Security

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

.agents/skills/plan-kanban-tasks/SKILL.md · 20 lines

What it actually says

Plan Kanban work

  1. 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.md exists.
  2. Produce one concise PDR covering the goal, current behavior, scope, exclusions, risks, dependencies, acceptance criteria, and focused tests.
  3. Split only when pieces can be implemented and validated independently. Concurrent tasks must have explicit path ownership and dependencies.
  4. 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.
  5. 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.
  6. 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

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. 10d ago First seen · 20 lines · 32 tokens per session scan A b5c661a74724

Subscribe to this mod's changes

plan-kanban-tasks is a skill published in the GitHub repository yylo-dev/yylo (58 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 294 once invoked, about $0.0002 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-30.