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 tolibear/goalbuddy --skill goal-prepgit clone --depth 1 https://github.com/tolibear/goalbuddyWrote 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/tolibear/goalbuddy/goal-prep)<a href="https://agentmods.dev/skills/tolibear/goalbuddy/goal-prep"><img src="https://agentmods.dev/badge/skills/tolibear/goalbuddy/goal-prep/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/tolibear/goalbuddy/goal-prep"><img src="https://agentmods.dev/badge/skills/tolibear/goalbuddy/goal-prep.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.00079 | $0.05367 |
| Opus 5 | $0.00039 | $0.02684 |
| Sonnet 5 | $0.00016 | $0.01073 |
| Haiku 4.5 | $0.00008 | $0.00537 |
Grade A, and why
goal-prep 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 9d 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.
This is a copy
100% identical to goal-prep — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal Prep
$goal-prep (Codex) or /goal-prep (Claude Code) prepares a GoalBuddy board. It does not start execution automatically, but the board and harness-specific starter command must be shaped so the next run continues into safe execution by default.
GoalBuddy is for autonomous, long-running Codex or Claude Code work where the PM thread may need to discover the work, define tasks, sequence them, delegate them, execute them, verify them, and keep going without the human decomposing every step.
The loop is:
raw user intent -> intake compiler -> goal oracle -> local work surface -> one active task -> receipt -> proof loop -> repeat
GoalBuddy's core invariant is:
Intent -> Oracle -> Surface -> Loop -> Proof
No oracle, no serious goal. A goal oracle is the observable signal that tells the PM whether the original owner outcome is actually true yet. It may be a test suite, browser walkthrough, demo transcript, generated artifact, benchmark, source-backed answer, release check, or final human decision. Weak proof creates weak goals, so record the oracle before shaping tasks and keep testing against it until final completion.
Invocation Boundary
There are two different modes:
$goal-prepor/goal-prep: prepare intake,goal.md,state.yaml, and the starter execution commands, then stop.- Codex
/goal Follow docs/goals/<slug>/goal.md.or Claude Code/goalbuddy Follow docs/goals/<slug>/goal.md.: execute the board, including Scout/Judge/Worker work.
This boundary is strict. $goal-prep is not a lightweight /goal; it is a board compiler.
This document is the prep-mode contract plus the shared board model. The execution contract lives in references/goal-execution.md next to this file; read it at the start of every Codex /goal or Claude Code /goalbuddy run. If it cannot be read, these execution invariants still hold: state.yaml is board truth; exactly one active task unless disjoint write scopes are proven; Scout and Judge tasks are read-only; Worker tasks write only inside allowed_files and run their verify commands; every completed, blocked, or escalated task gets a receipt; the goal completes only through a final Judge or PM audit that maps receipts and verification back to the original outcome (recording full_outcome_complete: true for continuous execution goals).
What ships with it
34 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.
- agents/config-snippet.toml 131 B
- agents/goal_judge.toml 2.9 KB
- agents/goal_scout.toml 1.7 KB
- agents/goal_worker.toml 3.0 KB
- agents/openai.yaml 653 B
- agents/README.md 1.1 KB
- references/goal-execution.md 24 KB
- scripts/apply-receipt.mjs 9.0 KB runs code
- scripts/check-can-stop.mjs 2.6 KB runs code
- scripts/check-goal-state.mjs 26 KB runs code
- scripts/check-update.mjs 3.9 KB runs code
- scripts/dispatch-task.mjs 11 KB runs code
- scripts/install-agents.mjs 1.2 KB runs code
- scripts/parallel-plan.mjs 6.3 KB runs code
- scripts/render-task-prompt.mjs 14 KB runs code
- surfaces/local-goal-board/assets/goalbuddy-mark.png 1171 KB
- surfaces/local-goal-board/examples/sample-goal/.gitignore 18 B
- surfaces/local-goal-board/examples/sample-goal/notes/T001-scout.md 94 B
- surfaces/local-goal-board/examples/sample-goal/state.yaml 3.3 KB
- surfaces/local-goal-board/examples/subgoal-parent/goal.md 95 B
- surfaces/local-goal-board/examples/subgoal-parent/notes/.gitkeep 1 B
- surfaces/local-goal-board/examples/subgoal-parent/state.yaml 1.5 KB
- surfaces/local-goal-board/examples/subgoal-parent/subgoals/T004-board-view/goal.md 77 B
- surfaces/local-goal-board/examples/subgoal-parent/subgoals/T004-board-view/notes/.gitkeep 1 B
- surfaces/local-goal-board/examples/subgoal-parent/subgoals/T004-board-view/state.yaml 1.2 KB
- surfaces/local-goal-board/README.md 3.1 KB
- surfaces/local-goal-board/scripts/lib/goal-board.mjs 70 KB runs code
- surfaces/local-goal-board/scripts/local-goal-board.mjs 21 KB runs code
- surfaces/local-goal-board/test/local-goal-board.test.mjs 37 KB runs code
- templates/agents.md 1.8 KB
- templates/goal-prompt.txt 105 B
- templates/goal.md 6.2 KB
- templates/note.md 379 B
- templates/state.yaml 5.3 KB
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.
- 9d ago First seen · 391 lines · 79 tokens per session scan A 39ca61602734
goal-prep is a skill published in the GitHub repository tolibear/goalbuddy (818 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 5,367 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to goal-prep, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.