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/rajkaria/boil-the-oceanWrote 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/rajkaria/boil-the-ocean/ocean-status)<a href="https://agentmods.dev/commands/rajkaria/boil-the-ocean/ocean-status"><img src="https://agentmods.dev/badge/commands/rajkaria/boil-the-ocean/ocean-status/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/rajkaria/boil-the-ocean/ocean-status"><img src="https://agentmods.dev/badge/commands/rajkaria/boil-the-ocean/ocean-status.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.00016 | $0.00227 |
| Opus 5 | $0.00008 | $0.00113 |
| Sonnet 5 | $0.00003 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
ocean-status 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 10d 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
Report the state of the boil-ocean run in this repo. Run these read-only commands
(<boil-ocean> = this plugin's root; scripts are also symlinked at ~/.claude/scripts/
when installed via install.sh):
bash <boil-ocean>/scripts/ocean-daemon.sh status— daemon liveness + sprint tabletail -20 .ocean/logs/daemon.log— recent scheduler activity (if present)- The last 2–3 entries of
.ocean/DECISIONS.md
Summarize in a few sentences: run status, sprints done/total and what's in flight,
whether the daemon is alive, the latest handoff notes, and any blockers verbatim.
If the run is blocked, state exactly what the human needs to decide, then how to
resume: fix → bash scripts/ocean.sh unblock → bash scripts/ocean-daemon.sh start.
$ARGUMENTS
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.
- 10d ago First seen · 19 lines · 16 tokens per session scan A 51ddec6547cb
ocean-status is a command published in the GitHub repository rajkaria/boil-the-ocean (2 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 227 once invoked, about $0.0001 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-31.
Other commands, from other repositories
fest-create
Create a new festival, phase, sequence, or task.
camp-intent
Capture an idea, list intents, or promote an intent to a festival.
camp-init
Create a new camp with the standard directory structure. A camp was previously called a campaign; camp init is the same command either way.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
fest-next
Get the next actionable festival task with full context.
fest-list
List all festivals with their status and completion percentage.