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 jeremysball/taskferry --skill using-taskferrygit clone --depth 1 https://github.com/jeremysball/taskferryWrote 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/jeremysball/taskferry/using-taskferry)<a href="https://agentmods.dev/skills/jeremysball/taskferry/using-taskferry"><img src="https://agentmods.dev/badge/skills/jeremysball/taskferry/using-taskferry/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/jeremysball/taskferry/using-taskferry"><img src="https://agentmods.dev/badge/skills/jeremysball/taskferry/using-taskferry.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00021 | $0.10210 |
| Opus 5.5 | $0.00008 | $0.04084 |
| Sonnet 5.5 | $0.00004 | $0.02042 |
| Haiku 4.5 | $0.00002 | $0.01021 |
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 — 772 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, settle. 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 Changed · +9 lines fc9b3c67fbbd
- 1mo ago Changed · +61 lines 0fe30983692c
- 1mo ago 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 2d ago), licensed MIT. It adds 21 tokens to every session and 10,210 once invoked, about $0.0001 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
plan-protocol
Guidelines for creating and managing implementation plans with citations.
plan-review
Criteria for reviewing implementation plans against quality standards.
opencode-delegation
Delegates tasks to OpenCode (opencode run) via delegation-core. Use when delegation-core selects OpenCode or a provider-agnostic harness is wanted.
soloncode-skin-skill
A tool that packages a visual theme for SolonCode Web UI as an installable ZIP file. SolonCode is a web-based coding interface, and a skin changes its colors, backgrounds, and overall appearance.
ui-ux-pro-max
UI/UX design intelligence expert for web and mobile applications. Use when designing interfaces, selecting color palettes, typography, visual styles, building landing pages, dashboards, or reviewing code for UX issues. Covers 50+ design styles, 97 color palettes, 57 font pairings, 99 UX guidelines, 25 chart types…
memory
Persistent, token-efficient project memory. When ON, maintains a .shob/memory/ folder of structured .md files so the full context of the project is NEVER lost across responses, sessions, or context compaction. Uses progressive disclosure — routes through a lightweight INDEX and loads only the files a task needs…