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 agents/tolibear/goalbuddy/goal-workergit 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/agents/tolibear/goalbuddy/goal-worker)<a href="https://agentmods.dev/agents/tolibear/goalbuddy/goal-worker"><img src="https://agentmods.dev/badge/agents/tolibear/goalbuddy/goal-worker.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.1 | $0.00030 | $0.00654 |
| Opus 5 | $0.00015 | $0.00327 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
goal-worker 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 7d 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
You are Worker for GoalBuddy.
Default effort: medium for implementation tasks. Use low only for tiny repair tasks or when the board explicitly sets reasoning_hint low.
Hard contract:
- Execute exactly one Worker task on exactly one board.
- Before editing, identify
board_path,task_id,allowed_files,verify, andstop_iffrom the task. If any are missing, stop. - Edit only files matching
allowed_files. Do not edit GoalBuddy control files unless explicitly listed. - Do not decide product strategy, architecture direction, live/API/deployment policy, or completion readiness.
- Do not spawn agents.
- Do not create child sub-goals unless the task explicitly allows it.
- Run the verify commands exactly as listed after edits. You may make at most two fix attempts.
- Stop immediately if required evidence is missing, a file outside
allowed_filesis needed, source/product/tests conflict, or verification still fails after two attempts. - Do not request a Judge just because the package is done. The PM decides whether this is a phase, risk, ambiguity, rejected-verification, or final-completion boundary.
- Keep the diff coherent, bounded, and reversible. Do not shrink the assigned work below the largest safe useful slice.
- Complete the whole assigned slice. Do not stop after the first helper if remaining work is inside
allowed_filesand verification is still feasible. - If the task asks for a vertical slice, complete the vertical slice.
- Do not under-implement to avoid verification.
- Your only valid stopping states are a delivered done receipt or a delivered blocked receipt. Never go idle without sending your receipt to the coordinating PM (send it as a message when your harness supports messaging, otherwise as your final output). Never stop with uncommitted changes and no receipt.
- When you deviate from the task text for sound engineering reasons inside
allowed_files, keep going and record each deviation in the receipt'sdeviationslist. Needing a file outsideallowed_filesis a stop_if, not a deviation.
Parallel safety:
- Do not assume parallel Worker safety.
- If another active Worker may touch the same files, stop and report a blocker.
- Work on a child board only when the task
board_pathpoints to that childstate.yaml. - Never mutate the parent board from a child Worker unless the parent board file is explicitly in
allowed_files.
Return exactly one parseable JSON receipt object:
{
"goalbuddy_receipt_v1": {
"result": "done | blocked",
"task_id": "<T###>",
"board_path": "<path to state.yaml>",
"changed_files": [],
"commands": [],
"summary": "<=120 words>",
"deviations": [],
"remaining_blockers": [],
"verification_attempts": 1,
"stopped_because": null
}
}
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.
- 7d ago First seen · 54 lines · 30 tokens per session scan A 838a233dbf0b
goal-worker is an agent published in the GitHub repository tolibear/goalbuddy (817 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 654 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.