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/jeremysball/taskferry/using-taskferrynpx skills add jeremysball/taskferry --skill using-taskferrygit clone --depth 1 https://github.com/jeremysball/taskferryWhat 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.00021 | $0.09369 |
| Opus 5 | $0.00010 | $0.04685 |
| Sonnet 5 | $0.00004 | $0.01874 |
| Haiku 4.5 | $0.00002 | $0.00937 |
Grade A, and why
using-taskferry 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 — 702 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taskferry Worker Backend
Taskferry dispatches long-running background agents — ferries — through the
taskferry CLI, on an external worker model rather than the host runtime.
Each dispatch runs in a copy-on-write overlay over a directory you name, and
settles into a changeset you accept or reject, so a ferry always produces a
verifiable diff before anything lands.
This file is the core loop: decide, dispatch, wait, verify, accept. Four resources hold the detail:
| Resource | Read it when |
|---|---|
resources/deciding-to-dispatch.md |
Before dispatching at all — the gate that decides whether this is ferry work |
resources/choosing-a-model.md |
Picking --model / --variant: tiers, role mapping, panels |
resources/monitoring-progress.md |
Waiting on a run, relaying progress, arming a fleet watch |
resources/failure-modes.md |
A dispatch crashed, lied, or silently answered the wrong question |
Sizing The Task Before Dispatching
See resources/deciding-to-dispatch.md for the gate and self-check before
routing a backlog item, bug, or fix through Taskferry — worktree creation, a
written brief, dispatch, wait, review are all costs to weigh against a
one-or-two-call Read/Edit/Grep. That resource's gate applies unchanged here;
this file assumes you've already passed it.
Always Use A Worktree
Every sandboxed ferry writes to a copy-on-write overlay, never the real
directory directly -- a rogue or mistaken dispatch cannot corrupt whatever
directory you point it at, worktree or not. taskferry result --diff also
handles HEAD drift safely rather than silently corrupting: if the
directory's real git HEAD has moved since dispatch (someone or something
checked out a different branch there while the task was in flight),
extraction reports a headDrift field and tries to recover via git apply --3way against the new HEAD. If recovery succeeds, the diff is applied and
the task settles pending for normal accept/reject; if the 3-way merge
fails, the task is auto-rejected with a changesetError; if recovery
couldn't be determined, the task settles pending with changesetError
for you to look at by hand. The diff is never silently computed against the
wrong tree, but extraction no longer refuses outright — it always records
something (taskferry#261 replaced the old fail-closed "HEAD moved" refusal
with this recover-or-flag behavior).
What ships with it
4 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.
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 · 702 lines · 21 tokens per session scan A 8f04dbeaa2fe
using-taskferry is a skill published in the GitHub repository jeremysball/taskferry (0 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 9,369 once invoked, about $0.0001 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
execute
Carry an approved task through to working, verified code.
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
at-zentao
Handle ZenTao (禅道) Bugs and Tasks end to end, including updating or writing back an item after code changes, managing Task status and hours, and reading linked Stories. Use for referenced ZenTao items, requirements, status changes, time entries, or post-implementation synchronization.
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
sdlc-draft-prd
Workflow to generate a comprehensive Product Requirements Document (PRD) detailing user stories, acceptance criteria, technical considerations, and metrics.
armada-gate
Run an evidence-gate checklist for each success criterion in the current phase. Use when checking if a phase is complete before marking it passed.