plate: Skill for Claude Code

.agents/skills/review-comment/SKILL.md

review-comment is a skill for Claude Code from udecode/plate. It costs 82 tokens per session (1,846 once invoked), scanned A, original, no licence file.

A workflow for reviewing Slate or Plate pull requests against the main branch. A pull request is a proposed code change, and the workflow uses research, code, and tests to support findings before drafting a GitHub review comment.

In plain words
What is it for?
Use it to review qualifying PRs, prove findings on the PR branch, or retrieve insights from Plate v2's earlier work.
Why use it?
It helps turn suspected problems into findings that are checked on the pull request's actual code rather than left as unverified suggestions.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is udecode/plate's own configuration. It tells Claude Code how to work on plate itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything plate configures →

Reuse

Borrowing it

Nothing to install: this file belongs to udecode/plate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/udecode/plate/next/.agents/skills/review-comment/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/udecode/plate

Made for: Claude Code.

Wrote 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.

agentmods badge for review-comment

README.md
[![agentmods](https://agentmods.dev/badge/skills/udecode/plate/review-comment/github.svg)](https://agentmods.dev/skills/udecode/plate/review-comment)
Your own site
<a href="https://agentmods.dev/skills/udecode/plate/review-comment"><img src="https://agentmods.dev/badge/skills/udecode/plate/review-comment/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.

agentmods 80×15 button for review-comment

Your own site · 80×15
<a href="https://agentmods.dev/skills/udecode/plate/review-comment"><img src="https://agentmods.dev/badge/skills/udecode/plate/review-comment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,846 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00082 $0.01846
Opus 5.5 $0.00033 $0.00738
Sonnet 5.5 $0.00016 $0.00369
Haiku 4.5 $0.00008 $0.00185

Measured today against content hash bb2cdecaf569, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-comment 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 today.

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.

.agents/skills/review-comment/SKILL.md · 76 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Changes

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.

  1. today Changed bb2cdecaf569
  2. yesterday Changed 498c8d13ed50
  3. 4d ago First seen · 76 lines · 82 tokens per session scan A f439353785e2

Subscribe to this mod's changes

review-comment is a skill published in the GitHub repository udecode/plate (16,680 stars, last pushed today), with no licence file. It adds 82 tokens to every session and 1,846 once invoked, about $0.0003 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-10-25.

Related

Other skills, from other repositories

ss-learn

Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…

bitjaru/styleseed · 73 tokens

isolating-product-facade-contracts

Plan and execute product isolation migrations to a facade plus contract layer in PostHog, following the Visual review architecture. Use when a product still exposes internals (models/logic/views) across boundaries and needs migration toward contracts.py + facade/api.py + presentation separation, with a PR strategy…

PostHog/posthog · 76 tokens

qa-frontend

Internal PostHog developer frontend/browser QA skill. Use only when a PostHog developer explicitly asks to run frontend QA, browser-test a PR, verify a UI flow against the local PostHog stack, use qa-frontend, or QA current frontend changes with browser/runtime evidence, or to make a feature reel (see reel mode…

PostHog/posthog · 216 tokens

walkeros-understanding-development

Use when contributing to walkerOS, before writing code, or when unsure about project conventions. Covers build/test/lint workflow, XP principles, folder structure, and package usage.

elbwalker/walkerOS · 41 tokens

reviewing-personhog-protocol

The full review process for personhog coordination-protocol changes — leases, fencing, handoffs, supervisors, failure budgets, warming, and changelog semantics. Use before pushing or requesting review on any personhog protocol changeset, when asked for an exhaustive or careful review of personhog code, and after any…

PostHog/posthog · 111 tokens

splitting-oversized-modules

Split an oversized Python module (a thousand-plus-line logic.py, models.py, api.py, or its test file) into a package of one module per concern, mechanically and provably without changing behavior. Use on a request to split / break up / decompose a god module or move functions out of one, once a human has agreed to…

PostHog/posthog · 197 tokens