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/lint)<a href="https://agentmods.dev/skills/eunji-jessi-jung/reef/lint"><img src="https://agentmods.dev/badge/skills/eunji-jessi-jung/reef/lint/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/lint"><img src="https://agentmods.dev/badge/skills/eunji-jessi-jung/reef/lint.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.00012 | $0.01152 |
| Opus 5 | $0.00006 | $0.00576 |
| Sonnet 5 | $0.00002 | $0.00230 |
| Haiku 4.5 | $0.00001 | $0.00115 |
Grade A, and why
lint 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 11d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reef:lint
Validate reef artifacts against the artifact contract. Reports errors, warnings, and info. Can auto-fix common issues.
Setup
Read this reference before doing anything else:
${CLAUDE_PLUGIN_ROOT}/references/artifact-contract.md
Voice
Direct and mechanical. Report findings plainly. No metaphors. No emojis.
Procedure
1. Locate the reef
Walk up from cwd looking for a .reef/ directory. That parent is the reef root. If not found, stop: "No reef found. Run /reef:init first."
2. Run lint
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/reef.py lint --reef <reef-root>
Parse the JSON output. Extract errors, warnings, and summary.
3. Report
If zero errors and zero warnings:
Lint passed — {N} artifacts checked, no issues found.
Otherwise, render a structured report:
Reef Lint — {N} artifacts checked
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Errors: {N}
{ARTIFACT-ID} {check} {message}
...
Warnings: {N}
{ARTIFACT-ID} {check} {message}
...
Group by artifact when multiple issues affect the same file. Show errors first, then warnings.
4. Auto-fix (if --fix argument or user requests it)
If the user passes --fix or says "fix" / "auto-fix" / "fix them", apply these fixes:
| Check | Auto-fix |
|---|---|
id_case |
Uppercase the id field in frontmatter |
filename_case |
Rename file to lowercase |
title_case |
Title-case the title field |
schema (missing field) |
Add field with sensible default: tags: [], relates_to: [], sources: [], known_unknowns: [], freshness_note: "TBD", freshness_triggers: [], aliases: [], notes: "" |
wikilink_sync (frontmatter has, Related missing) |
Add missing [[wikilink]] to ## Related section |
wikilink_sync (Related has, frontmatter missing) |
Add missing entry to relates_to with type: "relates_to" |
dangling_reference |
Remove the dangling relates_to entry (warn user) |
orphan |
Info only — cannot auto-fix (requires another artifact to link to this one) |
source_existence |
Info only — cannot auto-fix (source may have been renamed/deleted) |
freshness |
Info only — cannot auto-fix (requires /reef:update) |
key_facts_sources |
Info only — cannot auto-fix (requires code reading to add citations) |
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.
- 11d ago First seen · 121 lines · 12 tokens per session scan A 37705ba53836
lint is a skill published in the GitHub repository eunji-jessi-jung/reef (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,152 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.