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 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/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/jpicklyk/task-orchestrator/create-item"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/create-item.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00105 | $0.03724 |
| Opus 5.5 | $0.00042 | $0.01490 |
| Sonnet 5.5 | $0.00021 | $0.00745 |
| Haiku 4.5 | $0.00011 | $0.00372 |
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 13d 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 — 246 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 scope first from the SessionStart context. A ## Project Scope section (Active project plus a Config: line) carries a project rootId: it scopes reads and anchors new root-level items. A ## Personal Scope section (Personal root plus a Config: line) carries a personal root: it only anchors new items, and reads stay unscoped (no ancestorId/anchorId on read calls, which may show other projects' items). Without session context, read .taskorchestrator/config.yaml's top-level project.rootId (a file read, not an MCP call), which yields a project rootId only.
If a project 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 a personal root is known: the anchor-finding scan may run under it (query_items(operation="overview", anchorId="<personal root>", includeChildren=true)) — that finds an anchor, it does not read work. If no container there fits, create the item with parentId=<personal root>; never leave it at depth 0.
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.
- 13d ago Changed 088455286f0c
- 18d ago Changed · +2 lines 2434e883169c
- 21d ago Changed · +32 lines 0b3dc297bc84
- 1mo 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 (209 stars, last pushed 2d ago), licensed MIT. It adds 105 tokens to every session and 3,724 once invoked, about $0.0004 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
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.
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.
plan-tasks
Read an existing spec and propose a task breakdown — assesses separable work streams, proposes split, creates task files linked to the spec.
draft-issue
Draft a GitHub issue based on a discussion or requirements in the current conversation.
run-task
Run pending steps, then aftertask finalization; does not close the task.
load-spec
Load a feature spec, its linked tasks, and feature-level progress and gaps.