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 eunji-jessi-jung/reef/plugin install reefWrote 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/eunji-jessi-jung/reef/update)<a href="https://agentmods.dev/skills/eunji-jessi-jung/reef/update"><img src="https://agentmods.dev/badge/skills/eunji-jessi-jung/reef/update/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/eunji-jessi-jung/reef/update"><img src="https://agentmods.dev/badge/skills/eunji-jessi-jung/reef/update.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.00007 | $0.06468 |
| Opus 5 | $0.00003 | $0.03234 |
| Sonnet 5 | $0.00001 | $0.01294 |
| Haiku 4.5 | $0.00001 | $0.00647 |
Grade A, and why
update 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 563 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reef:update
Pull latest source code, re-extract specs, detect what changed, and produce an update report for human review. This is the "keep your reef alive" skill. /reef:health reports staleness; /reef:update fixes it.
Default mode is human-reviewed. Changes are presented as a curated report. You decide what to apply. Use --auto to apply everything without prompting.
Setup
Read these references before doing anything else:
${CLAUDE_PLUGIN_ROOT}/references/artifact-contract.md${CLAUDE_PLUGIN_ROOT}/references/methodology.md
Voice
Curious Researcher. Present-participle narration. No emojis. No exclamation marks.
Procedure
0. Check for an unfinished update report
Before doing anything else, check if .reef/update-report.json exists.
If it exists and has items with "status": "pending":
Count applied, pending, and skipped items. Then check staleness: compare the report's source_index_at against the current modification times of source files on disk (spot-check 5-10 files from the source index). If any have changed since the report was generated, the report is stale.
Report is fresh (sources unchanged):
Found an unfinished update report from {date}.
Applied: N items | Pending: M items | Skipped: K items
Options:
1. Resume — review remaining M items
2. Regenerate — re-scan sources and build a fresh report
Report is stale (sources changed since generation):
Found an unfinished update report from {date}.
Applied: N items | Pending: M items | Skipped: K items
Warning: sources have changed since this report was generated.
The report may be incomplete or outdated.
Options:
1. Regenerate — build a fresh report from current sources (recommended)
2. Resume anyway — apply remaining items (may miss new changes)
3. Discard — delete the old report and start fresh
On Resume: skip to Step 7 (present report and review loop) with the existing report.
On Regenerate or Discard: delete update-report.json and proceed from Step 1.
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.
- 12d ago First seen · 563 lines · 7 tokens per session scan A 75ef3077290c
update is a skill published in the GitHub repository eunji-jessi-jung/reef (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 6,468 once invoked, about $0.0000 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…