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.
npx skills add oalders/kitchen-sink --skill perl-reviewgit clone --depth 1 https://github.com/oalders/kitchen-sinkWrote 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/oalders/kitchen-sink/perl-review)<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.
<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>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.00056 | $0.00947 |
| Opus 5 | $0.00028 | $0.00474 |
| Sonnet 5 | $0.00011 | $0.00189 |
| Haiku 4.5 | $0.00006 | $0.00095 |
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.
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.mdandSTANDARDS.mdas 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).
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.
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 · 102 lines · 56 tokens per session scan A 721e55c8f2ea
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.
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.
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".
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…
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…
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.
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…