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/rdudov/task-agent/task-runnernpx skills add rdudov/task-agent --skill task-runnergit clone --depth 1 https://github.com/rdudov/task-agentWhat 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.00073 | $0.15481 |
| Opus 5 | $0.00036 | $0.07741 |
| Sonnet 5 | $0.00015 | $0.03096 |
| Haiku 4.5 | $0.00007 | $0.01548 |
Grade A, and why
task-runner 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 yesterday.
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 — 1,107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Runner
This skill launches a child CLI agent to execute a task from its task directory.
Use the standard single-child workflow by default. Use the dev-pipeline workflow when a task should run through the evidence-gated dev-pipeline lifecycle instead.
Before implementation, use the canonical no-code-first order: do nothing; remove or disable; configure or reuse; simplify; only then add the smallest necessary code and state why the observed gap required it. Independent review treats avoidable code or needless complexity as a defect.
Artifacts
The runner expects:
task.mdplan.md
It creates or updates:
trace.mdstatus.json.runner/prompt.txt.runner/runner.json.runner/runner.log.runner/review-admission.jsonfor the current launch,.runner/review-admission-commitment.jsonwhile a committed binding is waiting for its author to start, andreviews/admissions.jsonlfor every admission this number has madereviews/rounds.jsonlandreviews/infrastructure-obligations.jsonl, once a review round or a review outage happens
The child is asked to publish progress.json for long runs, and to place explicitly requested output files in deliverables/ with deliverables/manifest.json.
The dev-pipeline workflow also creates dev-pipeline/.
An application that already supervises the entire worker service or container
may use start --foreground and review --foreground. These forms keep the
same admission, binding, phases, review rounds and completion decision, but wait
for the child in the caller process instead of detaching a watcher that the
outer container would terminate. The recorded supervision durability is
caller_owned; foreground never supplies a missing assurance strategy or
reviewer.
Runner Selection
The child runner follows the parent CLI agent. task_runner.py owns that decision, so callers that never read this file get the same resolution. The order is:
- an explicit
--runner codex|claude|agent, which always wins; - the
TASK_AGENT_CHILD_RUNNERenvironment variable; - the nearest
claudeorcodexprocess ancestor; - a single vendor's session markers in the environment (
CODEX_THREAD_ID,CLAUDECODE), used only when no CLI ancestor is visible; - the documented fallback
codex.
What ships with it
29 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- scripts/__init__.py 161 B runs code
- scripts/application_adapter.py 9.5 KB runs code
- scripts/dev_pipeline_adapter.py 38 KB runs code
- scripts/git_publication.py 17 KB runs code
- scripts/pipeline_notify.py 4.6 KB runs code
- scripts/product_review.py 24 KB runs code
- scripts/review_admission.py 75 KB runs code
- scripts/task_completion.py 18 KB runs code
- scripts/task_contract.py 63 KB runs code
- scripts/task_engine.py 9.3 KB runs code
- scripts/task_phases.py 9.2 KB runs code
- scripts/task_runner.py 168 KB runs code
- scripts/task_workspace.py 24 KB runs code
- scripts/write_admission.py 44 KB runs code
- tests/test_application_adapter.py 20 KB runs code
- tests/test_dev_pipeline_adapter.py 46 KB runs code
- tests/test_git_publication.py 22 KB runs code
- tests/test_launch_failure.py 9.2 KB runs code
- tests/test_lifecycle_and_progress.py 30 KB runs code
- tests/test_process_supervision.py 22 KB runs code
- tests/test_product_review.py 40 KB runs code
- tests/test_review_admission.py 117 KB runs code
- tests/test_runner_resolution.py 15 KB runs code
- tests/test_task_contract.py 11 KB runs code
- tests/test_task_engine.py 9.7 KB runs code
- tests/test_task_phases.py 8.3 KB runs code
- tests/test_task_runner.py 33 KB runs code
- tests/test_task_workspace.py 18 KB runs code
- tests/test_write_admission.py 62 KB runs code
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.
- yesterday First seen · 1,107 lines · 73 tokens per session scan A 7640e3c3d3a6
task-runner is a skill published in the GitHub repository rdudov/task-agent (4 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 15,481 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…