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.
git clone --depth 1 https://github.com/publu/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/commands/publu/goalkeeper/help)<a href="https://agentmods.dev/commands/publu/goalkeeper/help"><img src="https://agentmods.dev/badge/commands/publu/goalkeeper/help/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/commands/publu/goalkeeper/help"><img src="https://agentmods.dev/badge/commands/publu/goalkeeper/help.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.00010 | $0.00307 |
| Opus 5.5 | $0.00004 | $0.00123 |
| Sonnet 5.5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
help 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 1mo 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
Explain goalkeeper to the user, concisely:
goalkeeper is a Stop-hook guard for Claude Code & Codex. It won't let this session end until the goals it is holding are provably complete. Every time the agent tries to stop, goalkeeper re-injects the unfinished checklist as the next instruction — so the agent keeps working instead of quitting early.
Commands
/goalkeeper:go <objective>— decompose an objective into goals and start working/goalkeeper:add <goal>— add one verifiable goal/goalkeeper:status— show mode and checklist/goalkeeper:mode [off|lite|standard|strict]— get/set strictness/goalkeeper:release— clear all goals and stand the guard down/goalkeeper:help— this message
Modes: off (disarmed) · lite (one nudge) · standard (until done) · strict (until done and independently verified).
Config (env): GOALKEEPER_DEFAULT_MODE sets the starting mode;
GOALKEEPER_MAX_LOOPS (default 30) caps continuations without progress so it
can never loop forever.
The agent keeps the loop honest by checking goals off as it finishes them:
done <id>, and in strict mode verify <id> once there's proof.
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.
- 1mo ago First seen · 29 lines · 10 tokens per session scan A 4c5c2ac3c5cc
help is a command published in the GitHub repository publu/goalkeeper (1 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 307 once invoked, about $0.0000 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 commands, from other repositories
lint-config
Show or edit AgentLint configuration.
lint-status
Show AgentLint status — coverage, effective policy, session activity.
edit
An interview-style command for editing the trigger words used by existing personas. Personas are predefined viewpoints, such as a developer, designer, or lawyer, that guide how work is approached.
update
Update Slime to the latest version.
fable-eval
Run the fable-mode eval suite (probes → pairwise judge → report). Costs tokens — runs headless claude many times. Optional arg: a probe id substring to filter.
decree
Issue a decree. Seats the organization on first use, then dispatches the teams.