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 rdudov/task-agent --skill task-runnergit clone --depth 1 https://github.com/rdudov/task-agentWrote 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/rdudov/task-agent/task-runner)<a href="https://agentmods.dev/skills/rdudov/task-agent/task-runner"><img src="https://agentmods.dev/badge/skills/rdudov/task-agent/task-runner/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/rdudov/task-agent/task-runner"><img src="https://agentmods.dev/badge/skills/rdudov/task-agent/task-runner.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 Agent Snooping · line 1146 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00073 | $0.16588 |
| Opus 5.5 | $0.00029 | $0.06635 |
| Sonnet 5.5 | $0.00015 | $0.03318 |
| Haiku 4.5 | $0.00007 | $0.01659 |
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 18d 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 — 1,182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Current review policy
Pre-author statement review accepts an explicitly configured isolated_same_provider assurance through the existing prepared-assurance seam. Such a reviewer must have read-only access and no repository write grant. Product statement validation accepts that admitted strategy. Unconfigured Codex↔Claude pairing remains unchanged.
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.
.runner/prompt.txt is also the readable record of what the child or reviewer
was told. It names one target repository as its path and multiple repositories
as a comma-separated path list, never as a Python Path or list
representation; a repository-less author prompt omits that line.
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. Once the durable pending launch claim exists, foreground supervision
releases the preparation ownership lock just as a detached launch does; live
process identity and the pending claim continue to refuse concurrent starts.
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 10 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.5 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 65 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 173 KB runs code
- scripts/task_workspace.py 25 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 32 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 121 KB runs code
- tests/test_runner_resolution.py 16 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 50 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.
- 18d ago Changed · +5 lines 549ab3031a6b
- 1mo ago Changed · +9 lines b4701b04bdee
- 1mo ago Changed · +61 lines b61a9b6e91db
- 1mo ago 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 7d ago), licensed MIT. It adds 73 tokens to every session and 16,588 once invoked, about $0.0003 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-31.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…