Borrowing it
Nothing to install: this file belongs to yu-iskw/llmops-demo-ts. 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/yu-iskw/llmops-demo-ts/main/.claude/skills/plan-task/SKILL.mdgit clone --depth 1 https://github.com/yu-iskw/llmops-demo-tsWrote 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/yu-iskw/llmops-demo-ts/plan-task)<a href="https://agentmods.dev/skills/yu-iskw/llmops-demo-ts/plan-task"><img src="https://agentmods.dev/badge/skills/yu-iskw/llmops-demo-ts/plan-task.svg" alt="Measured on agentmods" 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.00049 | $0.00390 |
| Opus 5 | $0.00024 | $0.00195 |
| Sonnet 5 | $0.00010 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
plan-task 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 3d 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 Task
Create a detailed implementation plan for the following task:
$ARGUMENTS
Planning Steps
- Research the codebase to understand current state relevant to this task
- Identify all affected packages (common, agents, backend, frontend)
- Break down into ordered tasks with clear dependencies
- Assign each task to an agent role (software-engineer, designer, qa, etc.)
- Identify risks and architectural decisions needed
Output Format
Produce a structured plan in exactly this format:
## Task Plan
### Overview
[One paragraph summarizing the goal]
### Tasks
1. **[Task title]**
- Description: [What needs to be done]
- Package/files: [Which files will change]
- Dependencies: [Which task numbers must complete first, or "none"]
- Complexity: [Low / Medium / High]
- Agent: [software-engineer / designer / qa / code-reviewer / security / sre-devops / legal-compliance]
2. **[Task title]**
- Description: ...
- Package/files: ...
- Dependencies: ...
- Complexity: ...
- Agent: ...
### Risks & Considerations
- [Breaking changes, migration needs, test gaps, performance]
### Architecture Decisions
- [Design choices that need to be made upfront]
Be specific about file paths and concrete changes needed. This output will be fed to /orchestrate to create a parallel execution plan.
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.
- 3d ago First seen · 57 lines · 49 tokens per session scan A d15fc795c03d
plan-task is a skill published in the GitHub repository yu-iskw/llmops-demo-ts (6 stars, last pushed 6d ago), licensed Apache-2.0. It adds 49 tokens to every session and 390 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-09-04.
Other skills, from other repositories
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
meta-meeting-to-workflow
Use this meta-skill instead of answering directly when the user has meeting notes, transcripts, recordings, or rough discussion notes and wants them converted into decisions, owners, follow-ups, tasks, issues, or shareable minutes through multi-skill orchestration.
meta-issue-to-pr-autopilot
Triages an issue, delegates the fix to sub-agent, drafts a PR description with summarize, and opens the PR via gh. Best used on small, well-scoped issues with clear acceptance criteria.
meta-github-pr-watch-digest
Inspect the user's open GitHub PRs / failing CI / new issues via gh, summarize into 3 buckets (to-review / awaiting-me / CI-red), and persist follow-ups to memory.
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
secretary
Workspace and research management — dispatch analyses, monitor running agents, manage workspaces and threads.