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/zebbern/agent-collab/goal-runnernpx skills add zebbern/agent-collab --skill goal-runnergit clone --depth 1 https://github.com/zebbern/agent-collabWrote 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/zebbern/agent-collab/goal-runner)<a href="https://agentmods.dev/skills/zebbern/agent-collab/goal-runner"><img src="https://agentmods.dev/badge/skills/zebbern/agent-collab/goal-runner.svg" alt="Measured on agentmods" 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 | $0.00062 | $0.00521 |
| Opus 5 | $0.00031 | $0.00260 |
| Sonnet 5 | $0.00012 | $0.00104 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
goal-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 4d 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.
What it actually says
Goal Runner
The companion (goal-companion.mjs) owns state, selection, and dispositions;
you own judgment. Follow the /goal:step choreography exactly — never
reimplement its bookkeeping by editing the goal file ad hoc.
Policy:
- One increment at a time.
next→start→ execute → verify → PR →record→ stop. The companion refuses a second in-progress item; do not work around the refusal. - Disclose. Announce each increment (and each delegation) in one line.
- Start before working. Call
startbefore any work on the increment begins — including delegated work — or the ledger's step-started→disposition gap understates reality and the retro must discard it. Ledger evidence, 2026-08-07: one of eight durations read 0min because work precededstart. - Delegate with judgment. Trivial work stays local. Deep analysis or a
second opinion goes to Codex, fast parallel implementation to Cursor, via
the
codex-delegation/cursor-delegationskills. Analysis and implementation are separate delegations when both are needed. - Refine once. If delegated work fails verification, refine the brief
with the failure evidence and re-delegate once; then record
blocked. - Blocked is a full stop. A blocked item blocks the goal;
nextrefuses until a human resolves it. Surface the reason; never guess past it. - Unattended never merges. A
/loop-driven or scheduled step works on agoal/<slug>/<itemId>branch, opens the PR, leaves the item in-progress, and stops; the next wake reconciles that PR (merged / closed / still open) before stepping. Merging stays human. - Honest dispositions.
mergedmeans the PR merged. Never invent progress, never record a disposition that has not actually happened, and if the companion or a delegate fails, report that instead of substituting your own output.
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.
- 4d ago First seen · 38 lines · 62 tokens per session scan A e58cd4f017c1
goal-runner is a skill published in the GitHub repository zebbern/agent-collab (32 stars, last pushed 19d ago), licensed Apache-2.0. It adds 62 tokens to every session and 521 once invoked, about $0.0003 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-30.
Other skills, from other repositories
turborepo-monorepo
Configure pipelines, set up local/remote caching, and run scoped tasks in a Turborepo monorepo. Use when you say: 'enable remote caching', 'optimize pipeline inputs/outputs', or 'filter builds to affected packages'.
vitest-testing
Vitest unit and integration testing patterns, commands, mocking (vi.mock), and coverage. Use when writing .test.ts files, configuring the test runner, or adding coverage thresholds.
vercel-deployment
Vercel deployment workflows, environment management, domain configuration, and build troubleshooting. Use when deploying, checking deployment status, reviewing build logs, or managing environments.
agent-hooks
Four lifecycle hooks every agent runs: on-session-start scans LESSONS-LEARNED.md, resumes checkpoints; on-pre-delegate verifies tracker issues, file partitions; on-post-delegate runs fast-review, CI checks; on-session-end runs the health checks, writes logs. Use when starting a new session, running pre-flight checks…
decomposition
Resolves task dependencies, generates machine-actionable delegation specs, structures phased subtask plans for multi-agent work. Use when writing delegation specs, resolving task dependencies, building phased subtask plans for multi-agent work, assigning work to sub-agents, or partitioning a feature into…
jira-management
Create and update Jira issues, epics, and sprints; manage backlog and sprint transitions. Use when you say: 'create a ticket', 'open a story', 'link an epic', 'start a sprint', or 'search the backlog'.