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 agentmods add skills/jpicklyk/task-orchestrator/create-itemnpx skills add jpicklyk/task-orchestrator --skill create-itemgit clone --depth 1 https://github.com/jpicklyk/task-orchestratorWrote 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/jpicklyk/task-orchestrator/create-item)<a href="https://agentmods.dev/skills/jpicklyk/task-orchestrator/create-item"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/create-item.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 | $0.00105 | $0.02585 |
| Opus 5 | $0.00053 | $0.01293 |
| Sonnet 5 | $0.00021 | $0.00517 |
| Haiku 4.5 | $0.00011 | $0.00259 |
Grade A, and why
create-item 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 4d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
create-item — Container-Anchored Work Item Creation
Create MCP work items intelligently from conversation context. This skill handles container anchoring, tag inference, structure decisions, and note pre-population so you don't have to.
Step 1 — Infer intent from conversation
Determine from context (or from $ARGUMENTS if provided):
- Title — what is the work item?
- Type — bug / feature / tech debt / observation / action item / general task
- Priority — high / medium / low (default: medium)
- Scope — single item, or feature with 2+ clear distinct subtasks?
If title or type cannot be inferred with confidence, use AskUserQuestion with concrete options. Do not ask open-ended questions.
Step 2 — Scan containers
Resolve the project rootId first: check session context for a rootId injected by the SessionStart hook, or read .taskorchestrator/config.yaml's top-level project.rootId (a file read, not an MCP call).
If a rootId is known:
query_items(operation="overview", anchorId="<rootId>", includeChildren=true)
Category containers (Bugs, Features, Tech Debt, etc.) are expected as direct children of the project root — anchor new items there. Exception: agent-observation items always stay at global depth 0, outside any project root, regardless of whether a rootId is known — they're process-global, not project-scoped.
If no rootId is known, fall back to an unscoped scan and the classification below (this is also the exact behavior from before project scoping existed):
query_items(operation="overview", includeChildren=true)
Classify the existing structure:
| Pattern | Classification |
|---|---|
| Depth-0 item with category-named children (Bugs, Features, etc.) | Hierarchical — project root exists |
| Category-named items at depth 0, no project root | Flat — use category containers directly |
| No items at all | Empty — offer to create project root |
Step 3 — Container anchoring
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.
- 4d ago First seen · 212 lines · 105 tokens per session scan A c234f84e4f4e
create-item is a skill published in the GitHub repository jpicklyk/task-orchestrator (205 stars, last pushed 1mo ago), licensed MIT. It adds 105 tokens to every session and 2,585 once invoked, about $0.0005 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.
Other skills, from other repositories
file-todos
File-based todo and task tracking in the todos/ directory. Use when creating, triaging, listing, or managing todo files, tracking work items, managing the backlog, converting PR comments to tracked tasks, or checking todo status and dependencies.
branch-surgery-pr-split
Split oversized or mixed-concern branches into smaller, reviewable PR stacks with safety refs, topology selection, parity audits, and merge sequencing. Use when a PR or branch is too large, difficult to review, mixed across concerns, conflict-prone, or needs to be decomposed without losing net changes.
workpackage-management
Use when performing workpackage actions: start, pause, complete, delete, defer, reorder, update progress, or check dependencies. Not for reading WP history or definitions.
cf-workpackage
Manage workpackage lifecycle — view status, list, create, start, pause, track progress, validate, complete, or delete. Use when the user mentions workpackages, asks to start or pause work, wants progress updates, or needs to change workpackage state.
cf-plan
Manage and view the development plan — status, progress, blockers, phases, and next steps. Use when the user asks about plan status, needs next-step recommendations, wants to create or modify the plan, or asks about phases and milestones.
do-it
Turn the current discussion into a task step and implement it — adds step to task file, updates spec if needed, then implements with review-fix loop.