perl-review

perl-review is a skill for Claude Code from oalders/kitchen-sink. It costs 56 tokens per session (947 once invoked), scanned A, original, MIT.

A rule-based reviewer for Perl files, including .pm, .pl, and .t files. It checks changed or named files against the project rules in STANDARDS.md and reports problems without editing the code.

In plain words
What is it for?
Use it after writing or changing Perl to check quoting, core-module use, URL building, test hygiene, and other rules listed in STANDARDS.md.
Why use it?
It finds departures from team standards without making automatic changes that you would need to review.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the kitchen-sink plugin — 9 skills, 20 commands, 12 hooks shipped together

Good fit Use it after writing or changing Perl to check quoting, core-module use, URL building, test hygiene, and other rules listed in STANDARDS.md.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oalders/kitchen-sink/perl-review
Install

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.

Any agent
npx skills add oalders/kitchen-sink --skill perl-review
Clone the repo
git clone --depth 1 https://github.com/oalders/kitchen-sink

Made for: Claude Code.

Or install kitchen-sink, the plugin that ships this one along with the rest of its 9 skills, 20 commands, 12 hooks.

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 perl-review

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/oalders/kitchen-sink/perl-review"><img src="https://agentmods.dev/badge/skills/oalders/kitchen-sink/perl-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 947 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 original 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.00056 $0.00947
Opus 5 $0.00028 $0.00474
Sonnet 5 $0.00011 $0.00189
Haiku 4.5 $0.00006 $0.00095

Measured 11d ago against content hash 721e55c8f2ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

perl-review 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.

skills/perl-review/SKILL.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Perl Review

Overview

Flag-only reviewer that applies the living standards in STANDARDS.md to Perl code. It reports violations grouped by rule and makes no edits and no commits — you apply fixes yourself.

STANDARDS.md is a table you edit freely. Adding or changing a rule needs no change to this file; the review reads whatever is in STANDARDS.md at runtime.

When to Use

  • You ask to review / Perl-review / check Perl against the project standards.
  • After writing or changing Perl (.pm, .pl, .t) on a branch.

Skip when: there is no in-scope Perl to review — report that and exit.

Dispatch this skill to a subagent

When invoked, dispatch the review to a general-purpose subagent via the Agent tool. Do not read every Perl file inline in the caller's context.

Why: reading the in-scope files and applying every rule is token-heavy, and the caller only needs the final grouped report.

How to dispatch:

  • Brief the subagent with this SKILL.md and STANDARDS.md as its spec (pass both paths), the working directory, and the review target (the diff, or the paths the caller named).
  • Require it to return only the grouped report and the one-line summary, in the format under "Report format" below.

If the user asks to run inline ("do it here so I can watch"), honour that — dispatch is the default, not a hard requirement.

What to Review

No paths given → the branch's committed changes against the base:

DEFAULT=$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's@^origin/@@')
if [ -z "$DEFAULT" ]; then
  for b in main master; do
    if git show-ref --verify --quiet "refs/heads/$b" \
      || git show-ref --verify --quiet "refs/remotes/origin/$b"; then
      DEFAULT=$b && break
    fi
  done
fi
BASE=$(git merge-base "$DEFAULT" HEAD)
git diff --name-only "$BASE"...HEAD

If origin/HEAD is unset, the loop falls back to whichever of main or master exists locally or on origin (so remote-only checkouts, e.g. CI, still resolve).

Read the full file on GitHub · 102 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 102 lines · 56 tokens per session scan A 721e55c8f2ea

Subscribe to this mod's changes

perl-review is a skill published in the GitHub repository oalders/kitchen-sink (4 stars, last pushed 11d ago), licensed MIT. It adds 56 tokens to every session and 947 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

no-bare-casts

Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.

prisma/orm · 52 tokens

code-review-csharp

Perform structured code reviews of C# source code covering naming conventions, performance, security, readability, and .NET best practices. Trigger phrases include "review this C# code", "check my C# for best practices", "analyze this C# class", "find issues in my C# code".

pnp/copilot-prompts · 66 tokens

solid-principles

SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length…

decebals/claude-code-java · 73 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-foss · 197 tokens

go-concurrency-safety

L1 supplement - audits Go-specific concurrency hazards in node client code: map iteration non-determinism, goroutine leaks, mutex ordering, panic boundaries, context cancellation.

PlamenTSV/plamen · 40 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