Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bonfire-systems/goalkeeper/plugin install goalkeeperWrote 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/bonfire-systems/goalkeeper/goal-clear)<a href="https://agentmods.dev/skills/bonfire-systems/goalkeeper/goal-clear"><img src="https://agentmods.dev/badge/skills/bonfire-systems/goalkeeper/goal-clear/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/bonfire-systems/goalkeeper/goal-clear"><img src="https://agentmods.dev/badge/skills/bonfire-systems/goalkeeper/goal-clear.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.00042 | $0.00360 |
| Opus 5 | $0.00021 | $0.00180 |
| Sonnet 5 | $0.00008 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
goal-clear 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.
What it actually says
You are operating the goal-clear skill. The gk CLI is python3 "${CLAUDE_PLUGIN_ROOT}/scripts/gk.py", abbreviated gk.
Flow
- Run
gk statusto see the active goal and its status. No active goal → tell the user and stop. - Confirm via AskUserQuestion before archiving (unless the goal is already
done— then clear is just bookkeeping):- Archive and clear (Recommended) — proceed.
- Cancel — abort, no changes.
- Run
gk clear --yes. gk appends the final log entry, moves the goal directory to.claude/goals/_archive/<slug>-<timestamp>/, writes the terminalactive.json, and — if a chain is in flight — marks itabortedwithout advancing (unreached links' contracts stay in place for re-use). - Relay gk's output: the archive path, and that
/goalor/goal-prepstarts a new goal.
Hard rules
- Never delete files. gk always archives; nothing is removed.
- Never run
gk clear --yeswithout the user's confirmation (except for an already-donegoal). The--yesflag exists so gk knows the question was asked — it is not a license to skip it. - Clearing kills any active chain — chains are not auto-resumed mid-stream.
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 · 22 lines · 42 tokens per session scan A 8da01c9ac8e5
goal-clear is a skill published in the GitHub repository bonfire-systems/goalkeeper (12 stars, last pushed 9d ago), licensed MIT. It adds 42 tokens to every session and 360 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 skills, from other repositories
skill-factory
A workflow that examines completed session work and turns reusable patterns into Claude Code skills.
session-wrap
Use when wrapping up a session before ending. 4 parallel subagents detect doc updates, repeated patterns, learning points, and follow-ups, then a verifier deduplicates and presents choices. Triggers on /session-wrap, session wrap, session cleanup, end of session.
caveman-help
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
relay
Session relay — compresses what's been done so far (writes a one-liner for /compact) and generates a "next task" prompt (a baton) for the user to hand off. Use on requests like "relay / hand off / next session / continue after compact / baton / handoff / clean up context and continue next task." Does not run /compact…
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…
strategic-compact
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.