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/health)<a href="https://agentmods.dev/skills/eunji-jessi-jung/reef/health"><img src="https://agentmods.dev/badge/skills/eunji-jessi-jung/reef/health/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/health"><img src="https://agentmods.dev/badge/skills/eunji-jessi-jung/reef/health.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.00005 | $0.02075 |
| Opus 5 | $0.00003 | $0.01038 |
| Sonnet 5 | $0.00001 | $0.00415 |
| Haiku 4.5 | $0.00001 | $0.00208 |
Grade A, and why
health 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reef:health
Read-only validation and freshness report. This skill does NOT modify artifacts. To fix issues, run /reef:update.
Setup
Read these references before doing anything else:
${CLAUDE_PLUGIN_ROOT}/references/artifact-contract.md${CLAUDE_PLUGIN_ROOT}/references/methodology.md
Voice
Curious Researcher. Use reef metaphor for status ("Your reef is aging", "3 artifacts growing stale"). Plain language for actions ("Run /reef:update to refresh"). No emojis. No exclamation marks.
Procedure
1. Locate the reef
Find the .reef/ directory in cwd or parents. Read project.json from the reef root.
2. Run script checks
Run both commands:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/reef.py lint --reef <reef-root>
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/reef.py diff --reef <reef-root>
These cover the seven mechanical checks:
- Orphan detection — artifacts with no incoming
relates_to(exceptSYS-roots, which are natural entry points). - Dangling references —
relates_totargets that do not resolve to an existing artifact file. - Source file existence —
sourcesrefs that no longer exist on disk. - Frontmatter schema — required fields present, valid enum values,
idmatches filename. - Key Facts without source links — Key Facts missing the
→citation syntax. - Wikilink/frontmatter sync —
## Relatedwikilinks do not matchrelates_toentries. - Freshness — source files changed on disk since the artifact's last write time.
3. Format the report
Render the health report as a text table using Unicode box-drawing characters. The report has three sections: domain coverage (headline), artifact health, and source detail (secondary).
Section 1 — Artifact Topology (headline)
Show a heatmap matrix of artifact density by service and type. This gives the user an instant visual of where the reef is deep vs thin.
Use shaded block characters to represent density:
- (empty) = 0 artifacts
░= 1-2▒= 3-4▓= 5-6█= 7+
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 · 197 lines · 5 tokens per session scan A 0f45da7a6530
health is a skill published in the GitHub repository eunji-jessi-jung/reef (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 5 tokens to every session and 2,075 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…